Skip to main content
Glama

Get Listing

get_listing
Read-onlyIdempotent

Get one published ADHD evaluation provider 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.6/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 and repeatability profile is fully covered by structured data. The description adds one genuinely new behavioral fact — that only *published* listings are retrievable, so drafts will not be returned — but says nothing about what happens on a missing or unpublished slug (error vs empty result).

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?

A single twelve-word sentence with the verb, cardinality and lookup key all front-loaded. There is no filler, no restatement of the title, and nothing that could be trimmed without losing information.

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 one-parameter read tool with full schema coverage and rich annotations, the description covers purpose, cardinality and the published-only constraint, which is sufficient to call it correctly. The only meaningful omission is failure behavior for an unknown or unpublished slug, since no output schema exists to document the response 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?

Schema description coverage is 100% and the single slug parameter already carries its pattern, length bounds and description in the schema. The phrase "by its slug" confirms the identifier role but adds no format, casing or source guidance beyond what the schema already enforces.

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 uses a specific verb-resource pair (get ... provider listing) and bounds the scope to a single published record identified by slug, which clearly separates it from the plural list_* and search_listings siblings without naming them. It falls short of a 5 only because it does not explicitly name the alternative tool an agent should pick for multi-record or keyword lookups.

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 words "one" and "by its slug" imply the lookup use case and the requirement that a slug already be known, so an agent can infer when this applies. However, there is no explicit when-to-use or when-not guidance, and nothing points to search_listings when a slug is unknown or to list_* when many records are needed.

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