Skip to main content
Glama

list_source_matches

Read-only

Lists import sources and their available matches with import status. Call without a source ID to see all sources, or with one to view its matches and missing imports.

Instructions

Sites this server can import matches from (for example the community's own match history), and for one source the matches it lists with their import status here. Call without source_id to list sources.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
source_idNo
only_missingNoOnly matches with a demo that are not imported yet.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered externally. The description adds useful substance — that sources include the community's own match history and that results carry per-match import status — but says nothing about the default page size, the 200 cap, or what happens to matches already imported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, but the dual-mode content is compressed into an awkward clause ('and for one source the matches it lists with their import status here') that forces a re-read. Splitting the two modes into separate front-loaded statements would cost no extra length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the mode split is covered. What is missing is enough on pagination/limit and on how import status values relate to import_matches, which matters for a tool whose output drives a follow-up import decision.

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 description coverage is only 33%; only only_missing is documented in the schema. The description meaningfully compensates for source_id by explaining that omitting it switches the tool to source-listing mode, but it never mentions limit or its default of 40, leaving one parameter undocumented in both places.

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 (importable match sites, e.g. community match history) and states the two modes: list sources, or list a source's matches with import status. It is a verb+resource statement an agent can act on, though the phrasing 'for one source the matches it lists with their import status here' is convoluted enough to slow comprehension.

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?

It gives an explicit routing rule: 'Call without source_id to list sources,' which tells the agent the conditional behavior of the single optional parameter. It does not contrast itself with list_matches or import_matches, so the agent must infer whether this or list_matches is the right entry point for already-imported matches.

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