Skip to main content
Glama

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

Recover a full Plus Code

recover_plus_code
Read-onlyIdempotent

Turn a short Plus Code back into the full code using a nearby reference point (coordinates, not a place name). 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>",
      "ref": "<ref>"
    },
    "name": "recover_plus_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesA point near the place.
codeYesA short (or full) plus code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 by structured data. The description adds only the input-form constraint on the reference point and says nothing about the proximity requirement for resolution or how an unresolvable code is reported.

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 front-loaded and waste-free. The second sentence is pure promotional link text pointing at the vendor's API catalog and contributes nothing to tool selection or invocation, so 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?

With only two fully documented parameters, complete annotations and no output schema, the description covers what an agent needs to call the tool correctly. The remaining gap is behavioral — no note on what a failure to resolve looks like — which is minor for a simple read-only conversion.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema by clarifying that 'ref' must be coordinates rather than a place name — a distinction the schema's 'A point near the place' does not make. It also implies 'code' may be short or full, which the schema hints at but the description reinforces.

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?

States a specific verb and resource — turning a short Plus Code back into a full code — and specifies the mechanism (a nearby reference point). It is unambiguously the inverse of the sibling shorten_plus_code, so an agent can route between the two without opening a schema.

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?

The parenthetical '(coordinates, not a place name)' is a genuine usage constraint that prevents a common misuse. What it lacks is an explicit statement of when to prefer this over shorten_plus_code or what to do if the short code cannot be resolved, but the context is otherwise clear.

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