Skip to main content
Glama

BRAINIAC Route & Delivery Optimisation

Encoded polyline encode/decode

route-optimization_polyline-codec
Read-onlyIdempotent

Encode or decode Google Encoded Polyline strings and optionally simplify with Douglas-Peucker. Price $0.01 USDC. POST /api/v1/route-optimization/polyline-codec. An unpaid call returns the x402 payment terms and does not run.

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": "route-optimization_polyline-codec"
  }
}

Input Schema

NameRequiredDescriptionDefault
decodeNodecode, value. Optional.
encodeNoencode, array. Optional.
simplifyNosimplify, value. Optional.
precisionNoprecision, value. Optional.

Output Schema

NameRequiredDescriptionDefault
pointsNopoints. Number.
encodedNoencoded. String.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds important operational context beyond annotations: the $0.01 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without running.

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?

The description is four short, front-loaded sentences with no wasted wording. Purpose, pricing, endpoint, and unpaid-call behavior are each presented once and in a sensible order.

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?

Given the output schema, annotations, and full schema description coverage, the definition is largely complete. It still leaves minor gaps around coordinate ordering for encode and the exact interaction between encode/decode and simplify, but nothing critical for a simple codec utility.

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 schema already explains each parameter. The description adds useful meaning by naming Google Encoded Polyline format and identifying Douglas-Peucker simplification, though it does not clarify whether encode and decode are mutually exclusive or how precision relates to either operation.

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?

The description states specific verbs and resources: encode or decode Google Encoded Polyline strings, with optional Douglas-Peucker simplification. This is clearly distinguishable from the route-planning siblings and leaves no doubt about the tool's function.

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 function is clear enough that usage is implied, but the description does not explicitly say when to choose encode vs decode, whether both may be supplied, or what prerequisites apply beyond the payment note. It provides context but no explicit when-to-use or when-not-to-use guidance.

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