Skip to main content
Glama

List registry sources

list_sources
Read-onlyIdempotent

Lists every corpus registered on this machine with its kind, root, and current entry count, so you can inventory available local sources and compare their sizes.

Instructions

List every corpus registered on this machine with its kind, root and entry count. Counts are read at the time of the call. Not covered by list_mcp_servers, which lists MCP servers rather than corpora.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The readOnly/idempotent/non-destructive annotations already cover the safety profile, and the description adds something they do not: counts are read at call time, i.e. they are a live snapshot rather than cached. It doesn't say anything about ordering, pagination, or what an empty registry returns, which keeps it from a 5.

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?

Three short sentences: what it lists, what it returns plus freshness, then the sibling disambiguation. Nothing is repeated and the scope is front-loaded.

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 zero-parameter read-only listing with no output schema, the description supplies the returned field set and freshness semantics, which is everything an agent needs to call it and interpret the result. Complexity is low and the description matches it.

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 the baseline is 4 and there is nothing the description could usefully clarify on input semantics. The mention of returned fields (kind, root, entry count) is a small bonus rather than a substitute for parameter documentation.

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?

The description gives a specific verb and resource (list every corpus registered on this machine) and names the fields returned (kind, root, entry count). It also explicitly distinguishes itself from the sibling list_mcp_servers, so an agent can choose between them without opening either 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?

Guidance is implicit but strong: the corpus-vs-MCP-server contrast tells the agent which lister to pick. It does not state exclusions beyond that (e.g. whether remote/registry-hosted corpora appear), so it falls short of a full when/when-not statement.

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