Skip to main content
Glama

groundhog.markets

Fetch a place

fetch
Read-onlyIdempotent

Connector form of forecast: the 7-day forecast of a place id from search as {id, title, text, url, metadata}. Otherwise prefer forecast, or markets for a market city. Keep the credits and link the url when you repeat numbers.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the safety bar is met. The description adds genuinely new behavioral context: the exact response shape and an attribution obligation ('keep the credits and link the url when you repeat numbers'). It does not state failure behavior for an unknown or non-search-derived id.

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?

Two short sentences with no padding, and the output shape and routing advice come early. The telegraphic style ('Connector form of forecast', 'Otherwise') costs a little readability but wastes no words.

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 one-parameter read tool with full annotation coverage, the description supplies the return shape (compensating for the missing output schema), the id provenance, the sibling routing, and the attribution rule. Only error/empty-result 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.

Parameters3/5

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

Schema coverage is 0%, so the description carries the burden for the single parameter. It does add meaning by constraining the id to one obtained from search, which the schema does not express. It stops short of saying what a place id looks like or whether ids from places are accepted.

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?

The description names the resource (a place id from search) and the payload (7-day forecast) plus the exact return shape {id, title, text, url, metadata}, so an agent knows what it gets back. It also distinguishes itself from forecast and markets. 'Connector form of forecast' is jargon, but the rest of the sentence resolves what the tool actually does.

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?

'Otherwise prefer forecast, or markets for a market city' explicitly routes the agent to two alternatives with the condition that selects them. The trigger for using this tool itself ('connector form') is stated in relative terms and requires the agent to infer that it is the wiring/connector variant of forecast, which is a small gap.

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