Skip to main content
Glama

Metrics, criteria and sources

list_metrics_and_sources
Read-onlyIdempotent

What the dataset holds: scoring lines with their scales and default weights, metrics with coverage, sources with licences, take-home pay models, newcomer regimes with each condition's id, presets, and the link-only sources. Pass kind for one part (kind "regimes", country "NL" lists the Dutch regimes and their conditions).

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_metrics_and_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOne part only; leave out for everything
countryNoISO alpha-2, with kind taxModels or regimes

Output Schema

NameRequiredDescriptionDefault
reportVersionYesThe report's shape version (now 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so the safety profile is covered. The description adds one behavioral detail beyond that: omitting kind returns everything, while supplying kind narrows to one part. It says nothing about the size or shape of the response, though an output schema exists that carries that burden.

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?

Two sentences, front-loaded with what is returned and followed by the scoping rule. The long comma-list of dataset parts is dense but each item carries real information about coverage; only minor trimming would be possible without losing content.

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 two-optional-parameter discovery tool with a full output schema and full annotation coverage, the description gives enough: what parts exist, how to scope, and a worked example. The remaining gap is the unaddressed overlap with list_sources, which matters because both surface source data.

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?

Schema coverage is 100% with an enum and field descriptions, so baseline is 3. The description rises above it by showing a concrete combined use ('kind "regimes", country "NL" lists the Dutch regimes and their conditions'), which clarifies the payoff of pairing country with kind rather than just restating that they go together.

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 the resource concretely by enumerating the catalog contents (scoring lines, metrics, sources, tax models, regimes, presets, link-only sources), so an agent knows this is a metadata/catalog listing tool. It is weakened only by using a noun phrase ('What the dataset holds') instead of a verb, and by never distinguishing it from the sibling list_sources, which overlaps on the 'sources with licences' part.

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 implied rather than stated: the enumeration of dataset parts suggests calling it to discover what's available before other tools. The only explicit guidance is about scoping via kind ('Pass kind for one part'), which is parameter behavior, not when-to-use vs alternatives. Nothing says when to prefer list_sources over this tool for source data.

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.