get_algae_profileGet a structured public algae diagnostic profile using the exact slug returned by search_algae.
| 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, so the agent knows this is a safe, non-destructive read operation. The description adds that the profile is 'public' and 'structured', and that the slug must be exact, which provides minor additional context. No contradiction with annotations, but no deep behavioral details beyond what annotations provide.
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 sentence of 15 words, front-loaded with the verb 'Get'. It contains no unnecessary words or repetition, and every part of the sentence contributes to understanding the tool's purpose and usage.
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?
With an output schema present (context signal), the description does not need to explain return values. The tool is simple (2 params, 1 required). The description covers the purpose, the prerequisite (slug from search_algae), and the nature of the profile ('public', 'structured'). It is largely complete, though it could briefly mention what the profile contains (e.g., algae identification details) but that is handled by the output schema.
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 coverage is 100% with both parameters having descriptions. The description reinforces that the slug must be 'exact' and from 'search_algae', adding slight extra context. Since the schema already describes the parameters well, the description does not add significant new meaning, earning a baseline score of 3.
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 verb 'Get' and the resource 'structured public algae diagnostic profile', and distinguishes it from sibling tools by specifying the slug must come from 'search_algae'. This immediately informs the agent of the tool's exact function and how it relates to other 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 says to use the slug returned by 'search_algae', providing a clear prerequisite and usage context. While it does not list alternative tools or when not to use it, the guidance is sufficient for an agent to determine the correct invocation sequence among many sibling get_* tools.
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.