Skip to main content
Glama

Levels Custom Apparel

Read a garment

get_product
Read-only

The facts of one garment: brand, fabric, fit, every colour with its sizes in stock, what it suits, its price before a logo and its link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe product's slug, from search_products

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description still adds real value by disclosing what the payload contains, notably that stock is per-colour-per-size and that the price is pre-logo. That pre-logo pricing detail is non-obvious semantics an agent would not get from annotations. It stops short of stating behaviour on an unknown slug.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence of dense enumerated content with no filler, and the return-value highlights are front-loaded. The phrasing 'its price before a logo and its link' is slightly telegraphic, costing a bit of readability, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing the return value, and it does so thoroughly by listing every field group. Combined with annotations covering the safety profile, an agent has enough to call it correctly; only error/not-found behaviour is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter at 100% schema coverage, the schema already fully documents 'slug' including its origin. The description adds nothing about the parameter's format or lookup failure behaviour, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly frames the tool as returning the full record for a single garment and enumerates the fields it holds (brand, fabric, fit, colours/sizes, suits, pre-logo price, link). The scope word 'one' implicitly separates it from search_products, but the verb is nominal ('the facts of') rather than an explicit 'read/retrieve', and no sibling is named. Clear, though not as sharp as a verb+resource+sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this instead of search_products, and no prerequisite noted. The only hint that it should follow a search lives in the schema text ('from search_products'), not the description. An agent must infer the search-then-fetch workflow on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources