Skip to main content
Glama

luxurygaragebuilders

Get Listing

get_listing
Read-onlyIdempotent

Get one published garage specialist 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's only added behavioral fact is the word "published", signaling that unpublished/draft listings are not retrievable — useful, but it says nothing about what happens with an unknown or unpublished slug (empty result 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?

One front-loaded sentence with no filler; the resource and the lookup key arrive immediately. It is arguably too terse rather than padded, since a clause on return shape or non-published behavior would earn its place.

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-only, fully annotated lookup with 100% schema coverage, the definition covers essentially everything needed to call it correctly. The only real gap is the absence of an output schema combined with no description of the returned listing shape.

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?

There is a single parameter and schema description coverage is 100%, with a regex pattern and length bounds already documented in the schema. The description only restates that the lookup is by slug, adding no format, casing, or validation semantics beyond the structured field.

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 ("Get") plus a precisely scoped resource ("one published garage specialist") and the lookup key ("by its slug"). The singular/"one" framing separates it from the list_* and search_listings siblings, though it never names them explicitly.

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 implied: fetch a single known listing when you already have its slug. There is no explicit when-not guidance or pointer telling the agent to use search_listings first to discover a slug, so the reader must infer the routing.

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