TogoMCP

by dbcls

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

get_pubchem_compound_id

Read-only

Resolve a compound name to its PubChem CID, returning a JSON-formatted ID for use in biomedical data queries.

Instructions

Get a PubChem compound ID (CID) for a compound name.

RETURNS the PubChem Compound ID(s) as a JSON-formatted string. On upstream/HTTP failure this tool does NOT raise — it returns a plain string beginning with "Error:" (not JSON). CHECK FOR the "Error:" prefix BEFORE parsing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "compound_name": "<compound_name>"
    },
    "name": "get_pubchem_compound_id"
  }
}

Input Schema

Name	Required	Description	Default
`compound_name`	Yes	Compound name, e.g. "resveratrol".

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Jul 25, 2026
- addedInput schema / properties / compound_name / description
```
Added value: +"Compound name, e.g. \"resveratrol\"."
```
First observedv0.1.0Jun 11, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond readOnlyHint and openWorldHint annotations, description discloses key error behavior: returns plain string with 'Error:' prefix (not JSON) on upstream/HTTP failure, and instructs to check for prefix before parsing. This is critical operational context not in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is compact and front-loaded: first sentence states the action, then critical error-handling details. Every sentence earns its place with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup tool with strong annotations and output schema, the description covers purpose, error behavior, and return format. It is complete for an agent to select and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the only parameter compound_name is already described with example. Description adds minimal extra meaning beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states it retrieves a PubChem compound ID (CID) for a compound name, with a clear verb+resource combination. It distinguishes from siblings like get_compound_attributes_from_pubchem by focusing on ID retrieval specifically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implies usage for looking up compound IDs by name and distinguishes via example. However, it does not explicitly state when to prefer this over related PubChem tools or exclude alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.