Skip to main content
Glama

list_feeds

Lists all AurAgrid data feeds with pricing in sats and USD, update intervals, sources, and free sample availability.

Instructions

List every AurAgrid feed: free or paid, price in sats and USD, update interval, source, free sample.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full disclosure burden, and it does useful work by stating that every feed is returned and enumerating the returned fields (free/paid, sats and USD price, interval, source, sample). It omits any mention of ordering, result size, or pagination behavior, and never explicitly says the operation is a read, which keeps it below the top score.

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?

A single colon-led sentence that front-loads the action and then lists the payload attributes; nothing is padded or repeated. Every clause maps to information the agent needs.

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 no-parameter list tool with no annotations and no output schema, the description supplies the essential missing piece, the shape of the returned feed data. It could be more complete by noting result size or whether the listing is exhaustive in one call, but nothing critical to invoking it is absent.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly gives no parameter discussion and instead spends its words on output content.

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 and resource ("List every AurAgrid feed") and names the concrete attributes returned, so the agent knows exactly what this tool produces. It stops short of distinguishing itself from siblings like fetch or get_sample, so an agent must infer that this is the enumeration/discovery entry point.

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?

"Every" implies the tool is the unfiltered full listing and takes no parameters, which suggests when it applies, but the description never states when to use it instead of fetch, get_quote, or get_sample. Usage is implied by the breadth of scope rather than explained.

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