Skip to main content
Glama

list_sources

Lists all configured sources with live health, event counts, and last errors so you can verify that a newly created source is actually ingesting data.

Instructions

List every configured source with its live health (status, events ingested, last error). Use it to confirm a source you created is actually ingesting.

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
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose that the call returns every configured source (no filtering) along with live health fields, which implicitly frames it as a read-only operation. It says nothing about permissions, pagination, cost on large source counts, or behavior when a source has never ingested, which are real gaps for a health-reporting tool.

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 sentences, zero filler, and the return payload is front-loaded before the usage hint. Nothing could be removed without losing information.

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

Completeness5/5

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

For a parameterless list tool with an output schema already documenting the return shape, the description covers purpose, scope (all sources, unfiltered), and the motivating use case. No information an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and schema coverage is 100%, so the baseline of 4 is tempered by the fact that there is simply no parameter meaning to add. The description correctly implies no arguments are needed by saying it lists 'every' source, but that is a light contribution rather than substantive semantics.

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 pairs a specific verb and resource ('List every configured source') with the exact payload the agent gets back ('status, events ingested, last error'), so the tool's function is unambiguous. It stops short of distinguishing itself by name from nearby siblings such as discover_source or create_source, leaving the agent to infer that this is the read-side counterpart.

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 to confirm a source you created is actually ingesting' gives a concrete selection scenario that ties naturally to the create_source sibling. It provides no explicit exclusions, such as when to prefer a discovery or diagnostics tool instead, so it lands at clear-context without routing rules.

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