Skip to main content
Glama

List Sources

list_sources
Read-onlyIdempotent

List where the marriage licence office data comes from, with the license and refresh of each source.

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 observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds value beyond them by disclosing what each returned record carries — license and refresh information per source — which is otherwise undocumented since there is no output schema. It stops short of noting size, ordering, or failure behavior, but little is at stake for a no-argument closed listing.

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, but the closing phrase 'with the license and refresh of each source' is slightly garbled and could be read as either license type or attribution/licensing terms.

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 trivial zero-parameter, closed-world listing with full annotation coverage and no output schema, the description supplies what an agent needs: what the list contains and what fields come back per entry. Only the exact return shape (field names, ordering) is left implicit.

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 no parameters, so there is nothing for the description to disambiguate; baseline for a zero-parameter schema is 4. The description correctly implies no filtering or paging inputs are needed.

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 pairs the verb 'List' with a specific resource ('where the marriage licence office data comes from') and states what each entry contains ('the license and refresh of each source'). It is clearly distinct from list_courses/list_places/list_products by domain, though it never explicitly contrasts itself with those siblings.

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: with zero parameters and a read-only listing scope, it is evident this is the entry point for discovering data provenance. However, there are no explicit conditions, prerequisites, or named alternatives (e.g., which tool to use once a source is identified).

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.

Resources