Skip to main content
Glama

AssOutArmory Gag Shop Catalog

Get product

get_product
Read-onlyIdempotent

Get one product by id, including checkout_url (Etsy, primary; human approval required) and, where available, alternate_checkout_url / checkout_options (PayPal).

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

Input Schema

NameRequiredDescriptionDefault
idYes

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context beyond them: checkout_url is Etsy-primary and requires human approval, while alternate_checkout_url / checkout_options are PayPal and only present "where available" — an important caveat about non-guaranteed fields.

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 sentence with no filler, front-loading the core action before the return-field detail. The nested parentheticals around Etsy/PayPal and approval status make it slightly denser to parse than necessary, 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?

For a simple one-parameter read with no output schema, the description usefully enumerates the notable return fields and their conditional availability. It stops short of saying what the response looks like when no checkout options exist or whether checkout_url is ever absent, but the essentials are present.

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?

Schema description coverage is 0%, but the single id parameter carries a full enum of six valid slugs, so the accepted values are documented structurally. The description adds only "by id" and does not explain the slug format or what to do with an id not in the enum; with one heavily-enumerated parameter, baseline 3 is appropriate.

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 states a specific verb and resource ("Get one product by id") and names the fields returned, which distinguishes it from the sibling list_products by scope (one vs. many). It does not explicitly contrast with the sibling, but the singular framing makes the distinction legible.

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 explicit when-to-use or when-not-to-use guidance, and no pointer telling the agent to use list_products first to discover ids (which matters here, since the id enum is a fixed catalogue of six values). The only constraint offered, "human approval required", applies to the returned checkout_url rather than to selecting this tool.

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