Skip to main content
Glama

agtmart sandbox store and agent survey

Get product details

get_product
Read-only

Full details for one sandbox product: description, GTIN, variants, stock, shipping, returns, and an estimate (price + shipping + estimated tax = estimated_total), also per variant.

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": {
      "product_id": "<product_id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context that this is a sandbox product and that the estimate is a computed price+shipping+tax total, but it says nothing about failure modes, latency, or whether an invalid ID returns empty vs. error.

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 dense sentence that front-loads the payload contents. Every clause names actual returned fields, so it earns its length, though the parenthetical formula slightly crowds the core statement.

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?

For a single-parameter read tool with no output schema, describing the returned fields (including the estimate formula) is exactly the right compensation. Only the missing product_id sourcing guidance and error behavior keep it from being complete.

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 description coverage is 0%, so the description must carry the meaning of product_id. All it conveys is 'one sandbox product', with no detail on ID format, source, or whether it must be an existing sandbox product ID — a gap that the schema does not fill.

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?

States a specific verb+resource ('Full details for one sandbox product') and enumerates the returned data (description, GTIN, variants, stock, shipping, returns, estimate). This clearly contrasts with a list/search tool, but it does not name or explicitly rule out the sibling search_products.

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

Usage Guidelines3/5

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

Usage is only implied: fetch full details for a single known product. There is no explicit when-to-use vs. search_products, no statement that product_id must come from a prior search, and no guidance on error behavior for an unknown ID.

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