Skip to main content
Glama

Get one car listing

get_listing
Read-onlyIdempotent

Full public details of one listing (spec, description, features, dealer, photos). Pass the listing id or its motifyme.co/marketplace url.

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": {
      "listing": "<listing>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
listingYeslisting id or url

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 a closed-world scope, so the safety profile is covered. The description adds that the payload is the 'full public' view, implying no private/authenticated data, but says nothing about error behavior for a bad id, missing listing, or partial data. Useful context, not rich behavioral disclosure.

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?

Two tight sentences with the payload description front-loaded and the input requirement second. Every clause carries information; no filler or repetition.

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 tool with full annotation coverage and no output schema, the description gives enough: what comes back, what input is accepted. Only edge-case behavior (not found, invalid id) is left unaddressed, which is minor at this complexity.

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?

With one parameter at 100% schema coverage, the schema already documents 'listing id or url'. The description restates it and adds the concrete URL shape (motifyme.co/marketplace/...), which is marginally helpful but not required syntax detail such as whether a slug or trailing path is accepted.

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+resource ('Full public details of one listing') and enumerates the returned sections (spec, description, features, dealer, photos), which clearly separates it from the search/list siblings. It stops short of explicitly naming a contrasting sibling like search_marketplace, so the differentiation is implied rather than stated.

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 only guidance is invocation-level: 'Pass the listing id or its motifyme.co/marketplace url.' There is no statement of when to prefer this over search_marketplace or get_dealer, and no note about what to do if the id is unknown or invalid. Usage is inferable (fetch details for a listing you already have) but not spelled out.

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