Skip to main content
Glama

fetch

Retrieves a specified feed and buys paid feeds over L402 only within your configured per-payment cap and budget.

Instructions

Fetch a feed. Paid feeds are bought over L402 only within the configured per-payment cap and budget.

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

Input Schema

NameRequiredDescriptionDefault
feedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses a meaningful trait — paid feeds are purchased over L402 subject to a per-payment cap and budget — but says nothing about return format, error behavior when a cap is exceeded, or whether free feeds behave differently.

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 wasted words, and the primary action is front-loaded. The payment constraint is dense but still earns its place.

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

Completeness3/5

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

For a simple one-parameter tool, the description covers purpose and payment mechanics but omits essential details: the expected format of the feed argument, what the tool returns, and how failures are surfaced. With no annotations or output schema, these gaps matter.

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?

The single required parameter "feed" has 0% schema description coverage, and the description does not clarify whether it expects a feed ID, URL, or name. The description adds no meaning beyond the parameter's name, leaving a significant gap.

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 opens with a specific verb+resource ("Fetch a feed"), making the core action unambiguous. It does not explicitly distinguish itself from siblings like get_sample or list_feeds, so it falls short of a 5.

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 second sentence implies that paid feeds are handled automatically via L402 within configured caps, which is useful usage context. However, it gives no explicit guidance on when to call fetch versus get_sample, get_quote, or list_feeds, leaving the agent to infer the workflow.

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

Deploy Server

Other Tools