Skip to main content
Glama

Describe product

describe_product

Full details of one product: input and output schema, examples, price, network and quality record.

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": "describe_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden; 'describe' plus the enumerated return contents convey a read-only lookup, and the disclosure of included fields compensates somewhat for the absence of an output schema. However, it says nothing about behavior for unknown slugs, rate limits, or whether returned schemas/examples can be large or paginated.

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?

A single front-loaded sentence that lists the returned content without filler. The enumeration is slightly dense but every element carries information.

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

Completeness3/5

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

For a one-parameter read tool with no output schema, enumerating return contents is a reasonable substitute for a response description. The missing piece is any identification of the input identifier and its expected form, which leaves a real gap given zero schema coverage.

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

Parameters2/5

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

Schema coverage is 0% and the single parameter 'slug' is never mentioned in the description, so the agent gets no help with what identifier to supply or its expected format. The description only implies 'one product' as the target, adding minimal meaning beyond the bare schema.

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 names the resource (one product) and enumerates what the response contains (schema, examples, price, network and quality record), which clearly separates it from siblings like buy_product, order_product, or search_products. The verb is only implicit in the tool name 'describe', but the read-only retrieval intent is unambiguous.

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 about when to use this tool versus search_products (for discovery) or try_product (for evaluation), nor any prerequisite such as needing a slug from a prior search. Usage is only inferable from the name and enumerated output fields.

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