Skip to main content
Glama

Licence & source register

list_sources
Read-only

Lists every data source behind active modules with operator, licence, attribution, update frequency, cache TTL and caveats. Use it to verify and cite upstream data.

Instructions

The machine-readable register of every data source behind the active Swissyphus modules: operator, licence, attribution string, update frequency, cache TTL and caveats.

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 observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description must carry the content burden, and it does by disclosing exactly what each entry contains, including caveats and cache TTL. It also scopes the result set to sources behind 'active' modules, which is real behavioral information; it stops short of stating the response format or whether the list can be large.

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?

A single front-loaded sentence with no filler; every clause adds a returned field or a scope qualifier. Slightly dense and jargon-laden ('machine-readable register'), but nothing is wasted.

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 no output schema and no parameters, the description has to convey the return payload, and the field enumeration does that well enough for an agent to decide whether to call it. It leaves the serialization shape and result size unstated, which is a minor gap for a simple zero-argument list 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 zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The enumerated field list adds interpretive value even though no inputs 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 names a concrete resource (a register of every data source behind the active Swissyphus modules) and enumerates its contents (operator, licence, attribution, update frequency, cache TTL, caveats), which is far more specific than the title alone. It doesn't explicitly differentiate itself from the sibling check_source_health, which sounds adjacent, but the verb metaphor ('register of ...') makes the enumeration purpose clear.

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?

Usage is only implied: an agent can infer this is the tool to call for licence/attribution/refresh-cadence metadata, but the description never states when to use it or when a sibling such as check_source_health is the better choice. No prerequisites, no exclusions.

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