Om MCP Tool Capabilities
Which Om MCP tools are read-oriented, which ones launch work, and which ones upload or create artifacts.
Not every Om MCP tool has the same operational weight. Some are fast, read-oriented checks. Some launch asynchronous work. Some create or upload artifacts. This page is the practical map for understanding what kind of operation you are approving when an MCP client asks to call an Om tool. For Data Access specifically, the current retrieval tools return Generated Data export URLs rather than inline molecule tables.
Read-oriented tools
Read and inspection
| Tool family | Representative tools | What they do |
|---|---|---|
| System | om_status, pricing_get, credits_get, users_profile | Inspect health, pricing, Wallet Credits, and account profile state. |
| Data Access discovery | datasets_catalog, datasets_generated_protein_uuids | Show Generated Data available to your account. |
| Jobs inspection | jobs_history, jobs_status, jobs_wait, jobs_export_json, jobs_get_synthesize_report_result, jobs_get_deep_diligence_result, jobs_download_artifact, jobs_get_artifact_url | Track existing jobs, retrieve outputs, and resolve artifacts. |
| Artifacts lookup | artifacts_get | Resolve artifact metadata by artifact ID. |
| Diligence reference | diligence_gene_keys_list | List available diligence gene keys and counts. |
| Vibe Video inspection | vibe_video_status, vibe_video_list | Inspect submitted discovery video requests for the authenticated user. |
Launch and retrieval tools
Tools that start work or request generated results
| Tool family | Representative tools | What they do |
|---|---|---|
| Diligence launches | diligence_search, diligence_gather, diligence_crawl, diligence_deep_diligence, diligence_synthesize_report, diligence_get_target_diligence_report, rag_search | Start search, gather, crawl, synthesis, deep diligence, or semantic retrieval workflows. |
| Data Access retrieval | binders_get_shards, binders_urls | Retrieve molecular binder and non-binder exports from Generated Data for a protein. |
| Hub launches | hub_submit and active hub_<model> tools | Launch active Hub model workflows. |
| Vibe Video requests | vibe_video_submit | Submit a discovery music video request for Om review. |
Upload and create tools
Tools that create or upload artifacts
| Tool family | Representative tools | What they do |
|---|---|---|
| Artifact creation | artifacts_create_upload_url, artifacts_finalize_upload | Create and finalize artifact upload flows. |
| Artifact upload | artifacts_upload_bytes | Upload bytes into the Om artifact store for downstream use. |
Why this matters
Keep manual MCP tool approval on. Read-oriented tools are lower-risk than launch or upload tools. Diligence and Hub launches can start billable or long-running work, Data Access retrieval can expose licensed data links, Vibe Video submission creates a reviewed media request, and artifact tools can create or upload new objects into your account workflow.
Practical approval guidance
- Approve
om_statusandpricing_getearly to verify the connection. - Review Diligence, Data Access, Hub, and Vibe Video requests before approving them.
- Review artifact upload tools especially carefully, because they create or upload new inputs.
- Use natural-language prompts, but understand that the client may choose a launch-capable tool underneath.