get_disease_profileGet a structured public aquatic disease profile using the exact slug returned by search_diseases.
| 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, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds that the profile is 'public' and 'structured', which adds minor context. No contradictions with annotations.
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?
The description is a single, front-loaded sentence with no unnecessary words. It conveys purpose and prerequisite efficiently. 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?
Given that an output schema exists (indicated by context signals), the description does not need to detail return values. It covers the resource type (disease profile), domain (aquatic), and the required input source (search_diseases). A minor addition about what the structured profile includes (e.g., symptoms, treatments) could be helpful but is not essential.
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%, so the schema already documents both parameters (slug and language). The description mentions 'exact slug' but does not add new semantic detail beyond what's in the schema. Baseline score of 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 retrieves a structured aquatic disease profile using a slug from search_diseases. This specifies the resource (disease profile), action (get), and domain (aquatic disease), effectively distinguishing it from sibling get_* tools for other entity types.
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: use the exact slug returned by search_diseases. This provides clear context on when to use this tool (after searching for diseases). It does not explicitly list when not to use it or mention alternatives, but the prerequisite is well-defined.
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.