Skip to main content
Glama

Get Listing

get_listing
Read-onlyIdempotent

Get one published home lift company 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 readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds one genuinely useful behavioral constraint, 'published' (unpublished entities presumably are not returned), but says nothing about what happens when the slug does not exist or does not resolve to a published record.

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?

A single front-loaded sentence with no filler, which is appropriate for a one-parameter read tool. The slightly awkward 'home lift company' phrasing costs a bit of clarity but not length.

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 simple, fully annotated, single-parameter read, the description covers the core operation and identifies the returned entity type. With no output schema, it could say more about the response shape and not-found behavior, but nothing essential for invoking the tool is missing.

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 coverage is 100% and the single slug parameter is fully documented with pattern and length constraints in the schema. The description only restates 'by its slug' and adds no lookup semantics beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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') and a single resource ('one published home lift company') retrieved by slug, so an agent knows this is a single-item lookup rather than a list or search. The only weakness is that the description calls the resource a 'home lift company' while the tool name says 'listing', leaving a slight domain-mapping ambiguity.

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 only implied: the agent can infer this is for when it already has a slug, as opposed to search_listings or the list_* siblings. It never states when to prefer this over search_listings or what to do if only a name is known, so guidance is adequate but incomplete.

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