Skip to main content
Glama

groundhog.markets

Search places

search
Read-onlyIdempotent

Connector form of places, for clients that only call search and fetch: places by name, City, ST, airport code or lat,lon as {results: [{id, title, url, text}]}; pass an id to fetch. Otherwise prefer places, forecast or markets.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

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 cover read-only, idempotent, non-destructive semantics, and the description adds value beyond them by disclosing the return envelope {results: [{id, title, url, text}]} and the id-to-fetch follow-up path. It does not mention result limits or empty-result behavior, but the key behavioral facts are present.

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

Conciseness4/5

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

Compact and front-loaded, with the routing rule stated before the detail. The semicolon-chained clauses make it slightly run-on, but no sentence is wasted.

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 single-parameter tool with annotations and no output schema, the description covers purpose, accepted inputs, return shape, and fallback routing. Only pagination/result-count behavior is unaddressed, which is minor here.

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 0% (only "query": string), so the description carries the burden, and it does: the query may be a name, City/ST, airport code, or lat,lon. That materially exceeds what the schema says, though it doesn't demonstrate an exact format for the lat,lon case.

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 the specific resource and accepted lookup keys: "places by name, City, ST, airport code or lat,lon." The framing "connector form of places" immediately distinguishes it from the full places tool, though the phrase is somewhat implementation-flavored rather than describing the operation directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit selection rule: use this for clients that only call search and fetch, "Otherwise prefer places, forecast or markets," and "pass an id to fetch." Both the when-to-use and the alternatives are named with conditions attached.

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