get_medicine_profileGet a structured public aquarium medicine profile using the exact slug returned by search_medicines.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Exact single-segment slug returned by the related Atlarium search tool. | |
| language | No | Optional preferred response language: it, en or es. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | ||
| tool | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / slug / descriptionPrevious value: -"Single safe public Atlarium slug without path separators."New value: +"Exact single-segment slug returned by the related Atlarium search tool."Output schema / properties / generated_atRemoved value: -{
- "type": "string"
-}Output schema / requiredPrevious value: -[
- "data",
- "generated_at",
- "tool"
-]New value: +[
+ "data",
+ "tool"
+]Input schema / properties / language / descriptionAdded value: +"Optional preferred response language: it, en or es."Input schema / properties / slug / descriptionAdded value: +"Single safe public Atlarium slug without path separators."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, making the safety profile clear. The description adds only that it returns a 'structured public aquarium medicine profile', which is mildly helpful but does not elaborate on errors, rate limits, or response format. With annotations present, this is adequate.
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?
A single, front-loaded sentence that conveys the core purpose and prerequisite without any waste. Every word 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 simple 2-parameter tool with full annotations and an output schema (not shown but present), the description is sufficient. It explains the key dependency and purpose. Missing a brief note on the return structure, but the output schema covers that.
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% with both parameters already described in detail (slug: from related search tool; language: optional enum). The main description reaffirms the slug source but adds no new meaning beyond the schema. Baseline 3 is appropriate.
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?
The description clearly states the tool gets a structured public aquarium medicine profile using the exact slug from search_medicines. This is a specific verb-resource pair with a clear dependency, distinguishing it from sibling get_* tools.
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 description explicitly states the prerequisite to use the slug returned by search_medicines, guiding the agent to first search then retrieve. It does not explicitly exclude other usage scenarios, but the context of siblings makes it clear this is for medicine profiles only.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.