Skip to main content
Glama
Sign In

Polyform

by org.polyform
OverviewDiscussionsAdmin

geo_location_brief

Read-only

Location brief (bundle) — One call for a US place — pass an address OR lat+lon: normalized address + county/state + current conditions + active weather alerts. JSON. Price: $0.02 USDC (Base, via x402).

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": {
      "address": "<address>"
    },
    "name": "geo_location_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNooptional latitude
lonNooptional longitude
addressYesUS address (or use lat+lon)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and non-destructive. Description adds valuable context: JSON output, USD C pricing via x402, US-only scope, and the bundled response contents. It doesn't cover rate limits or auth, but annotations lower that burden.

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?

One dense, front-loaded sentence conveys purpose, inputs, output components, format, and price. No filler or repeated schema content.

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?

For a tool with no output schema, the description adequately explains return categories, input alternatives, scope, JSON format, and price. The address-required conflict and lack of explicit sibling guidance are the main gaps.

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

Parameters2/5

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

Schema coverage is 100% so a 3 baseline would normally apply, but the description's 'address OR lat+lon' claim conflicts with the schema, which requires address. This is actively misleading for an agent deciding whether to pass coordinates alone.

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?

Description clearly defines a bundled US-place lookup: normalized address, county/state, current conditions, and active alerts in one call. The 'bundle' phrasing distinguishes it from sibling geocoding and weather tools, even though it doesn't name them.

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?

Description communicates when to use it: when you need a US place's location details plus current weather and alerts in a single call. It does not explicitly name alternatives or exclusion cases, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Polyform toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources