Skip to main content
Glama

Get Listing

get_listing
Read-onlyIdempotent

Get one published sleep clinic 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 by structured data. The description does contribute one genuine behavioral fact beyond that: the word "published" tells the agent unpublished listings are out of scope and will not be returned. It says nothing about behavior when the slug is unknown (empty result vs. error) or what a returned record contains, so it adds only partial value.

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 sentence, zero filler, with the resource and the lookup key front-loaded. Nothing is redundant with the title and nothing could be cut without losing information.

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 single-parameter read with full annotation coverage the bar is low, and the definition is callable as written. However, with no output schema the description could reasonably say what a returned listing looks like or what happens on a missing/unpublished slug, and it leaves both silent. It is complete enough to invoke correctly but not complete enough to predict the result.

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 a full pattern, length bounds, and its own description, so the schema does the heavy lifting. The description only echoes it with "by its slug" and adds no format, casing, or sourcing guidance. Baseline 3 is correct when the schema is self-sufficient.

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?

"Get one published sleep clinic by its slug" gives a specific verb (get), a concrete resource (a sleep clinic, clarifying that a 'listing' is a clinic), a cardinality (one), and a lookup key (slug). An agent can distinguish it from search_listings on the basis of the description alone. It stops short of a 5 because it never names the sibling it is not, leaving the search/list partition to 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?

The phrase "by its slug" implicitly signals the precondition (you must already have a slug), which is real but unstated guidance. There is no explicit when-to-use, no when-not-to-use, and no pointer to search_listings for agents that only have a name or category. Adequate for a trivial lookup, but the routing guidance is left to inference.

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