Skip to main content
Glama

Show a catalog item

get_item
Read-only

Show one item in full by slug: its price, reviews, details and buy (the call that orders it). An unknown slug answers item_not_found. With your passport (your app's sign-in, the Authorization header or passport_token), a kit your owner bought also shows update_available: the newer version with the same main version number that is free for your owner, and the one buy call that gets it (null when nothing newer is free). The project blueprint read with your passport shows your owner's promo: used true once your owner had the free one (search_catalog always shows the general offer).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "webhook-inbox"
    },
    "name": "get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesItem slug from search_catalog.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "slug": "webhook-inbox"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
  3. Changed1 schema field changed
    • changedInput schema / properties / passport_token / description
      Previous value: -"Not needed on this public tool; accepted and ignored."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  4. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / passport_token
      Added value: +{
      +  "description": "Not needed on this public tool; accepted and ignored.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / slug / description
      Added value: +"Item slug from search_catalog."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the read-only/destructive annotations: it discloses the unknown-slug error (item_not_found), that passport auth comes via Authorization header or passport_token, that update_available is conditional on an owner-purchased kit and null when nothing newer is free, and that the promo's used flag flips once the free item is consumed. That is exactly the kind of conditional-return disclosure annotations cannot carry.

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?

Front-loaded with the core purpose and free of filler, but the passport and promo sentences are dense nested clauses that take real effort to parse on first read. Every sentence earns its place; the sentence structure could be simpler.

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

Completeness5/5

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

With no output schema and only two parameters, the description carries the return-value burden well: it covers normal fields, the error case, the conditional update_available field and its null semantics, and the promo flag. Nothing an agent needs to call this correctly or interpret the response is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that passport_token is an amp_ token used only when there is no app sign-in and no header can be sent, and that supplying it changes which fields come back rather than just how the call is made.

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

Purpose5/5

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

States a specific verb and resource ("Show one item in full by slug") and enumerates what comes back (price, reviews, details, the buy call). It also distinguishes itself from search_catalog by noting that search_catalog shows the general offer while this tool surfaces the owner-specific promo.

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

Usage Guidelines4/5

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

Names search_catalog as the general-offer alternative and makes the passport/no-passport condition explicit, so the agent knows which call to pick. It stops short of an explicit "use this when / do not use this when" statement, but the routing context is clear.

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.