Skip to main content
Glama

Get Listing

get_listing
Read-onlyIdempotent

Get one published auction house or platform by its slug.

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_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe listing slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the meaningful constraint that only *published* listings are retrievable, which is real information beyond the annotations. It does not disclose the not-found behavior or any visibility/permission scoping.

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

Conciseness5/5

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

One short sentence with the action front-loaded and no filler. Every word contributes: verb, cardinality, resource, publication filter, and lookup key.

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 tool whose annotations cover safety, this is close to sufficient. The gap is that no output schema exists, so the description is the only place that could indicate what a returned listing contains (identity fields, categories, related entities) and it does not.

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 100% and the single slug parameter carries its own pattern, length bounds and description. The phrase "by its slug" only restates the schema's semantics without adding format or lookup behavior detail, 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?

A specific verb ("Get") plus a specific resource ("one published auction house or platform") and a stated lookup key ("by its slug"). The word "one" implicitly contrasts with the list_* siblings, but no sibling is named, so differentiation requires a small inference.

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?

"by its slug" implies the precondition for use, and "published" hints that unpublished entities are out of scope. However, there is no explicit routing against search_listings or the list_* tools, and no statement of what happens when the slug is unknown or the listing is unpublished.

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