Skip to main content
Glama

List News Sources

list_news_sources
Read-onlyIdempotent

The news sources (RSS feeds, sites, YouTube channels, podcasts) the user follows — what list_news reads from. At most 10. Use it before adding sources, to skip ones already there.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety needs no restating. The description adds genuinely new behavioral facts: the collection is capped 'at most 10', which matters for pagination expectations and for deciding whether results are exhaustive.

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?

Two short sentences, front-loaded with the resource definition, then the usage rule. No filler, and the parenthetical type list does real work in telling the agent what a 'source' is.

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 zero-param read with rich annotations it covers what is returned at a category level, the size cap, and the workflow position. Return shape (fields per source, ordering) is not described, though that is a minor gap absent an output schema.

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?

Zero parameters, so baseline 4 applies; there is nothing for the description to disambiguate. The cap-of-10 note usefully frames the result set even though no inputs exist.

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

Purpose5/5

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

States a specific verb (list) and resource (news sources), enumerates the source types returned (RSS feeds, sites, YouTube channels, podcasts), and ties itself to the sibling consumer with 'what list_news reads from'. An agent can distinguish it from list_news and add_news_source without opening any schema.

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?

'Use it before adding sources, to skip ones already there' gives a concrete trigger and implicitly points at add_news_source as the alternative. It stops short of stating when-not-to-use (e.g., when the user just wants feed content, which is list_news).

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