Retrieve a specific culture medium from BacDive using its numeric DSMZ medium ID, returning composition, growth conditions, and citation.
Retrieve detailed information about a specific culture medium from BacDive using its numeric DSMZ medium ID. Returns the full medium composition, growth conditions, and citation.
| Name | Required | Description | Default |
|---|---|---|---|
| medium_id | Yes | The numeric DSMZ medium ID (e.g. 1, 5, 196). |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It usefully discloses what is returned (full composition, growth conditions, citation), which is valuable since there is no output schema, but it says nothing about error handling for bad IDs, rate limits, or authentication needs. Adequate but incomplete for a no-annotation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with zero filler; the identity of the resource and its lookup key are front-loaded, followed by the return payload. Every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read tool with no output schema, the description covers the essentials: what it fetches, by what key, and what is returned. The only gap is the absence of any error or failure-mode guidance, which keeps it short of fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single required parameter is documented in the schema with its type, minimum, and examples. The description restates 'numeric DSMZ medium ID' but adds no syntax or format detail beyond what the schema already provides, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (retrieve) and resource (culture medium) and identifies the lookup key as the numeric DSMZ medium ID, which implicitly separates it from the sibling search tool. It does not explicitly name bacdive_search_culture_medium as the alternative, so the differentiation is implied rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The usage condition is implied: use this when you already hold a numeric DSMZ medium ID, versus searching when you don't. There is no explicit 'use X instead when Y' routing and no statement of prerequisites or behavior on invalid/nonexistent IDs, so the guidance remains at the implied level.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.