Skip to main content
Glama

The source registry

list_sources
Read-onlyIdempotent

The curated list of sources: what each measures (with a plain definition), coverage, licence, whether it may be redistributed, how it is fetched (endpoint, CORS, key) and who vetted it, plus link-only pages such as Numbeo and WeatherSpark. Filter by metric or country; pass a place to get the publisher's page for it.

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
cityNoA city id or name in the dataset, to fill in each publisher's page for it
accessNo
metricNoMetric id, e.g. pm25, rent_1bed, sunshine_hours
countryNoISO alpha-2: only sources covering this country

Output Schema

NameRequiredDescriptionDefault
reportVersionYesThe report's shape version (now 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description usefully adds that the output mixes full registry records with link-only stub pages (Numbeo, WeatherSpark) and that passing a city changes what is returned. It says nothing about ordering, result volume, or whether link-out entries ever require network fetches, which would have resolved the mild tension with openWorldHint=false.

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 dense paragraph that front-loads the registry contents and reserves its last clause for filtering behaviour, so a reader gets the payload shape first. The long parenthetical field inventory is efficient compression, though it is arguably redundant with the output schema and crowds out the access parameter.

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 an output schema present, the description need not explain return values — yet it spends most of its budget doing exactly that, which is harmless but displaced effort. The filter semantics are covered; the only genuine gap is the undocumented access enum, which leaves an agent guessing at one of four optional parameters.

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 coverage is 75% and the three documented parameters (city, metric, country) are already explained in the schema. The description adds real meaning for city — it yields 'the publisher's page for it' — but the fourth parameter, access, has no schema description and no mention in the description either, so the enum values api/bulk/curated/link-out remain unexplained anywhere.

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 specific resource — a curated registry of data sources — and enumerates what each entry carries (definition, coverage, licence, redistribution rights, fetch method, vetting) plus link-only pages like Numbeo and WeatherSpark. That is far more than a restatement of the name. It stops short of 5 because it never distinguishes itself from the sibling list_metrics_and_sources, so an agent must infer the split.

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 gives concrete usage context: filter by metric or country, and pass a place to get the publisher's page for it. That tells the agent how to shape a query but offers no exclusions and names no alternative tool for the overlapping 'sources joined to metrics' case, which is implied to exist by the sibling list_metrics_and_sources.

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.