Skip to main content
Glama

list_sources

Read-onlyIdempotent

Lists AI news sources with URLs, categories, and collection status, including last success, last error, and consecutive failures, so you can check which sources work.

Instructions

Every Source with its URL, default Categories and collection state.

    The state is when it was last tried, when it last succeeded, its last error and
    how many collections in a row it has failed. The last error is kept after a success,
    so with 0 failures in a row it is from before `last_success_at`. Use it to check
    which Sources work.
    

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_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the lower bar applies; the description still adds real value by decoding the state fields and explaining the counterintuitive rule that the last error persists after a success. That '0 failures means the error predates last_success_at' caveat is exactly the kind of detail an agent would otherwise misread.

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?

It is front-loaded with the payload contents before the interpretive detail, and every sentence about state carries information. The middle explanation is slightly wordy with the backticked field name and could be tightened, but nothing is padding.

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?

With zero parameters and an output schema present, the definition only needs to frame the call and help interpret results, which it does. The one remaining gap is that it does not say how to act on a failing source, though that is arguably out of scope for a read tool.

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 no parameters, which is the baseline-4 case. The wording 'Every Source' correctly signals that the result is unfiltered and complete, so an agent will not hunt for a filtering argument that does not exist.

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 states a specific verb-and-resource pair ('Every Source with its URL, default Categories and collection state') and enumerates the fields returned. It distinguishes itself from action-oriented siblings like collect_now by being a plain enumeration, though it never names an alternative explicitly.

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?

'Use it to check which Sources work' gives one concrete reason to call the tool, but there is no guidance on when not to use it or what to call instead for adjacent needs such as triggering a collection. Usage is implied rather than framed against the siblings.

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