get_equipment_profileGet a structured public equipment product profile using the exact slug returned by search_equipment.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Exact safe slug path 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: -"Safe public Atlarium slug path made of one or more path segments."New value: +"Exact safe slug path 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: +"Safe public Atlarium slug path made of one or more path segments."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, which accurately characterize this as a safe, read-only operation. The description adds useful context that the profile is 'public' (no auth barrier beyond the api key), and specifies the input constraint. No contradictions.
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, concise sentence that front-loads the core action and resource, then adds the essential prerequisite constraint. Every word is necessary; no fluff or repeated information.
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 the low complexity (2 parameters, simple schema, no nested objects), clear annotations, and an output schema that handles return value documentation, this description is adequate. It provides the key context about data source (slug from search) and scope (public profile). Users have enough to invoke the tool correctly.
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 both parameters are well-documented in the schema. The description adds value by explaining the relationship with search_equipment ('returned by') and clarifies the 'language' parameter is optional and its use case ('preferred response language'). This provides meaning beyond the schema's enum listing.
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 specifies the verb ('Get'), the resource ('structured public equipment product profile'), and a unique constraint ('using the exact slug returned by search_equipment'). This differentiates it from sibling tools like search_equipment (which searches) and get_product_profile (which gets a different product type).
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 required input format ('exact slug returned by search_equipment'), implying that the user must first call search_equipment. It does not explicitly list when not to use it or alternative tools, but the sibling context and distinct resource name provide clarity.
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.