Skip to main content
Glama

List sources

list_sources
Read-onlyIdempotent

List the bookseller catalogs Near Fine searches, each with its bookseller and the countries it serves. Pass a country to see only the sources that serve buyers there. When the buyer has signed in, their favourite booksellers carry favourite: true.

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
countryNoOnly list sources serving buyers in this country (ISO 3166-1 alpha-2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavioral context the annotations cannot: what each entry contains and that signed-in buyers get a favourite: true marker. It does not discuss pagination or result size, keeping it from a 5.

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

Conciseness5/5

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

Three short sentences, front-loaded with what is listed, then the optional filter, then the conditional return detail. Every sentence carries information and none repeats the title.

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

Completeness5/5

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

For a single optional-parameter read tool with no output schema, the description supplies the return shape (bookseller, countries served, favourite flag), the filter behavior, and the sign-in condition. An agent has everything needed to call it and interpret the result.

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 100% and the country parameter already documents the ISO 3166-1 alpha-2 pattern and filtering semantics. The description's 'serve buyers there' restates that filter rather than adding new meaning such as behavior on unknown or unmatched country codes, so baseline 3 applies.

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 uses a specific verb and resource: 'List the bookseller catalogs Near Fine searches,' and even names the fields returned (bookseller, countries served). It does not explicitly distinguish itself from siblings like search_books or list_alerts, though the domain is clearly different, so it stops short of a 5.

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?

The sentence 'Pass a country to see only the sources that serve buyers there' implies when to use the filter, but there is no explicit when-to-use framing, no prerequisites, and no reference to alternatives for related tasks. Usage is implied rather than stated.

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