Skip to main content
Glama

fetch

Force retrieval for a specific concept, entity, and date, bypassing cache freshness to obtain current data despite stale cached results.

Instructions

Force a fetch for one (concept, entity, date), bypassing cache freshness.

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": {
      "concept_id": "<concept_id>",
      "entity_type": "<entity_type>",
      "entity_id": "<entity_id>",
      "date": "<date>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
entity_idYes
concept_idYes
entity_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true; the description adds the causal explanation — cache freshness is deliberately bypassed — which accounts for the non-idempotent, non-read-only profile and tells the agent this call has side effects on cache state. It still omits failure behavior, throttling, and how expensive a forced fetch is.

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?

A single front-loaded sentence with no filler; the scope key comes before the behavioral trait. It is efficient, though its brevity shades into under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an open-world, non-idempotent operation with four undocumented required parameters, the description leaves the agent guessing on date format, entity_type vocabulary, and the consequences/cost of a forced fetch. An output schema exists, so return values need not be described, but the input-side gaps are substantial.

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 0% with four required parameters, so the description carries the full burden. It names the three conceptual axes (concept, entity, date), which maps loosely onto concept_id/entity_id/entity_type/date, but gives no date format, no valid values for the free-text entity_type (no enum is defined anywhere), and no clarification of how entity_id and entity_type interact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('force a fetch') and a precise scope key ('one (concept, entity, date)'), plus the distinguishing cache-bypass trait. However, what is actually being fetched — a data value, an observation, an indicator series — is never named, so the tool's output subject remains vague and the wording partly echoes the name 'fetch'.

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?

'Bypassing cache freshness' implies the condition for use (when cached values are stale or untrusted), which is real but implicit. No explicit when-not guidance, no mention of cost or of siblings like consume_concepts or crawl_status, and no prerequisites (auth, rate limits) are stated.

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