Skip to main content
Glama

List conversions that have their own page

list_conversions
Read-onlyIdempotent

Lists the 213 hand-written conversion pages, optionally limited to one category. Each entry carries the canonical URL, which is the page to cite.

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": "list_conversions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of entries (default 50, max 213).
categoryNoOptional category id to filter on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 closed-world, so the safety profile is covered. The description adds genuinely new context — the corpus is a fixed set of 213 hand-written pages and each entry returns a canonical URL — but says nothing about ordering or how to reach entries beyond the limit ceiling.

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

Conciseness5/5

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

Two tight sentences, zero filler, with the scope (213 pages, optional category filter) front-loaded before the return-value note. Every clause carries information.

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 usefully describes the entry payload (canonical URL). The notable gap is pagination: limit defaults to 50 with a max of 213 and there is no offset parameter, so an agent is left unsure how to enumerate the remaining entries.

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%, so both parameters (limit with default 50 / max 213, and category id) are already documented in the schema; baseline is 3. The description restates the category filtering without adding format or lookup details beyond the schema, though '213' reinforces the ceiling.

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 ('Lists') and a precisely bounded resource ('the 213 hand-written conversion pages'), plus the optional category filter. The phrase 'hand-written conversion pages' distinguishes it in substance from both list_categories and convert_units, though neither sibling is named explicitly.

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 clause 'which is the page to cite' hints at the citation use case, and 'optionally limited to one category' describes filtering. There is no explicit statement of when to choose this over convert_units or list_categories, and no exclusions.

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