Skip to main content
Glama

A maker's official offers page

offers_page
Read-onlyIdempotent

The address of a car maker's own page of current offers (rebates, special APRs, lease deals), and of a model's page where one can be built, with whether the maker lists national offers at all and when the address was checked. Use it to point someone to the maker's official offers before comparing a rebate with a special APR (rebate_vs_apr). Returns links only, not the offers themselves, which change often and can vary by region.

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": {
      "make": "<make>"
    },
    "name": "offers_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesThe car maker, like Toyota or Ford
modelNoModel, like Corolla Cross, for the model's own offers page where there is one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / make / description
      Previous value: -"Make, like Toyota"New value: +"The car maker, like Toyota or Ford"
    • changedInput schema / properties / model / description
      Previous value: -"Model, like Corolla Cross"New value: +"Model, like Corolla Cross, for the model's own offers page where there is one"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: it says only links are returned, that the offers themselves change often and vary by region, and that a 'when checked' timestamp is included. That freshness caveat is exactly the kind of context structured fields cannot carry.

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?

Three sentences, all load-bearing, with the scope stated first and the sibling cross-reference and output caveat following. The opening sentence is dense and stacked with parallel clauses, which costs a little readability but wastes no words.

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?

With no output schema, the description compensates by characterizing the return payload (links, national-offer flag, check date). Combined with full schema coverage and read-only annotations, an agent has nearly everything needed; only pagination/error behavior is unaddressed, which is minor for a link lookup.

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%, so both parameters are already documented with examples in the schema. The description hints that model is only used 'where there is one', which lightly reinforces its optionality, but adds no new semantics. Baseline 3 applies 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?

The description states a specific resource (a maker's official offers page, plus a model build/offers page) and enumerates what comes back: the address, whether national offers are listed, and the check date. It is clearly distinguishable from rebate_vs_apr. It loses a point only because it opens with a noun phrase ('The address of...') rather than a verb, making the tool's action slightly indirect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit usage instruction — 'Use it to point someone to the maker's official offers before comparing a rebate with a special APR' — and names the sibling (rebate_vs_apr) it precedes. There are no explicit when-not conditions, but the role in the workflow is unambiguous.

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