Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Tire age from its DOT code

tire_age_from_dot
Read-onlyIdempotent

How old is a tire? Decode the DOT code's week and year of manufacture and the plant, and the age today. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "code": "<code>"
    },
    "name": "tire_age_from_dot"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoDate to measure the age at, YYYY-MM-DD (default today).
codeYesThe date code ("2319") or the whole DOT number ("DOT U2LL LMLR 2319").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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 covered. The description adds value by stating exactly what the operation yields (week/year of manufacture, plant, age today), which is a meaningful disclosure for a tool with no output schema; it omits edge cases such as handling of invalid or 3-digit codes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single functional sentence is well front-loaded and wastes nothing, but the trailing marketing line ("More APIs from FitzTopPicks: https://...utm_...") is pure noise that does not help an agent select or invoke the tool, and it dilutes an otherwise tight definition.

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 two-parameter, read-only decoding tool with full schema coverage and no output schema, the description covers inputs and the shape of the returned facts sufficiently. Only the handling of malformed codes and the exact age unit are left unstated, which is a minor gap.

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 both parameters are documented in-schema, including the flexible "2319" vs. full "DOT U2LL LMLR 2319" input formats and the asOf default. The description mirrors the age-as-of-today behavior but adds no format or validation meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Decode the DOT code's week and year of manufacture and the plant, and the age today" names a specific verb and resource and enumerates the concrete outputs, which lets an agent distinguish it from sibling tire tools like decode_tire_size or tire_load_index.

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 framing question "How old is a tire?" implies the usage context, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no reference to the tire-sizing siblings as alternatives despite their presence in the catalog.

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