Skip to main content
Glama

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

Shorten a Plus Code

shorten_plus_code
Read-onlyIdempotent

Shorten a full Plus Code (Open Location Code) near a reference point, for showing with a town 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": "shorten_plus_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe reference point, like "51.37,-1.22".
codeYesA full plus code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 meaningful context that shortening depends on proximity to a reference point, but omits what happens when the reference is too far away or what form the result takes.

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

Conciseness2/5

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

The first sentence is tight and front-loaded, but the trailing marketing sentence ('More APIs from FitzTopPicks: ...utm_source=mcp-api...') is pure promotional filler that consumes roughly half the description without helping an agent select or invoke the 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?

There is no output schema, so the description should clarify that the return value is a shortened code (and possibly its relationship to the reference). That is only implied, and the proximity failure mode is unaddressed, leaving a modest gap for a two-parameter tool.

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, so the baseline is 3. The description reinforces the relationship between 'code' and 'ref' ('near a reference point') but adds no format, distance, or validity constraints beyond the schema.

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 and resource ('Shorten a full Plus Code (Open Location Code)') plus the reference-point condition, which is enough to distinguish it from the sibling recover_plus_code. It stops short of naming the inverse operation explicitly, so an agent must infer the pairing.

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 phrase 'for showing with a town name' implies the display use case, but there is no explicit when-to-use/when-not guidance and no routing to recover_plus_code for the reverse operation. Usage is implied rather than stated.

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