Skip to main content
Glama
inboxd
by 47star

list_sources

Discover supported source IDs, collector health, coverage, and latest content timestamps to verify archive availability before treating empty search results as missing data.

Instructions

Discover supported source IDs, collector health, coverage and latest content timestamps.

Stored record counts include metadata entities and deleted records; they are not active message counts. Inspect collector coverage before treating an empty result as source absence. Specify source when the task already identifies one, to avoid unrelated source metadata.

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
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description does substantial work: it warns that record counts include metadata entities and deleted records and are not active message counts, and that empty results may reflect collector coverage gaps rather than source absence. These are non-obvious behavioral caveats an agent could not infer from the schema. It stops short of covering permissions, rate limits, or return shape.

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?

Four short sentences, front-loaded with the capability statement before the caveats. Each sentence carries distinct information with no filler. The third and fourth sentences are slightly abrupt relative to the rest but still earn their place.

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 one-optional-parameter discovery tool with no annotations and no output schema, the description covers what is returned, the caveat about count semantics, and how to avoid false 'no source' conclusions. Nothing critical for correct invocation appears missing, though naming the response fields more concretely would have closed the remaining gap.

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?

Schema description coverage is 0% for the single optional 'source' parameter, so the description must compensate. It does partially: 'Specify source when the task already identifies one, to avoid unrelated source metadata' conveys that omitting it returns all sources and that passing it narrows the response. Format or accepted ID values are still not stated, so the meaning added is directional but incomplete.

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 combination ('Discover supported source IDs, collector health, coverage and latest content timestamps'), making clear this is a source-catalog/health discovery tool rather than a message-reading tool. It is clearly distinguishable from siblings like get_message or search_messages, though it never names them 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?

It provides real usage guidance: 'Specify source when the task already identifies one, to avoid unrelated source metadata' tells the agent when to use the filter, and 'Inspect collector coverage before treating an empty result as source absence' tells the agent how to interpret results. However, there is no explicit statement of when not to use this tool or which sibling to prefer for message-level retrieval, so guidance is contextual rather than comparative.

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