Skip to main content
Glama

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

Tire load index

tire_load_index
Read-onlyIdempotent

How much weight does a tire load index carry (e.g. 98 = 750 kg), or which index covers a load? More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tire_load_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNolb (default) or kg, with minLoad.
indexNoA load index (0-170) or a dual pair like "121/118".
minLoadNoLoad per tire to carry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 profile is covered. The description adds the concrete mapping example (98 = 750 kg), which helps confirm output scale, but says nothing about the default unit (lb) applying when no unit is supplied, nor about what is returned when neither mode parameter is given.

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 functional sentence is tight and front-loaded, but roughly half the text is a promotional URL for other APIs that provides zero value to an agent selecting or invoking this tool. Removing it would make this a crisp two-clause definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, zero-required conversion tool with no output schema, the description covers the two usage modes but not the fallback behavior when no parameters are passed or when both are. Adequate but with a clear gap around the all-optional parameter set.

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%, including the unit enum and the dual-pair format for index, so the baseline is 3. The '98 = 750 kg' example reinforces index semantics, but all three parameters being optional leaves the description silent on precedence if both index and minLoad are supplied.

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 both directions of the conversion explicitly — index-to-weight ('98 = 750 kg') and weight-to-index ('which index covers a load') — which distinguishes it from siblings like tire_speed_rating or decode_tire_size. It is phrased as a question rather than a verb+resource statement, but the resource (tire load index) and operation are unambiguous.

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 two-clause question implies when to reach for it (you have an index, or you have a target load), but there is no explicit when-not guidance and no named alternative among the sibling tire tools. The caller must infer that index and minLoad are mutually exclusive modes.

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