Skip to main content
Glama

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

Supported coordinate formats

coordinate_formats
Read-onlyIdempotent

The coordinate formats convert_coordinates reads and writes, with example spellings. 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": "coordinate_formats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 fully covered structurally. The description adds only that entries include example spellings, which is modest extra context about the payload shape rather than richer behavioral detail such as ordering or count.

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 opening sentence is tight, front-loaded, and earns its place by naming both the content and the consuming tool. The second sentence is pure promotional boilerplate for unrelated APIs, adding no value to an agent selecting or invoking this tool.

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?

With no output schema and no parameters, the description carries the burden of explaining the return value, and 'with example spellings' only partially does so — it does not say whether the result is a list of format names, a mapping, or per-format examples. For a simple reference tool this is adequate but leaves a real gap about what the agent will actually receive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the schema to describe and no parameter meaning to add. The baseline of 4 applies; the description correctly does not waste space restating an empty input contract.

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 identifies a specific resource (the set of coordinate formats) and ties it directly to the sibling convert_coordinates, clarifying that this tool describes what that tool accepts and emits. It is not framed as an action verb ('List...'), but the noun phrase plus the 'example spellings' detail makes the purpose unambiguous and distinguishable from convert_coordinates itself.

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 relationship to convert_coordinates is stated, implying this is a reference lookup to consult before or alongside a conversion, but there is no explicit when-to-use clause, no statement of when it is unnecessary, and no naming of alternatives such as identify_coordinate. Usage must be inferred from the sibling reference.

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