Skip to main content
Glama

scout_catalog

Read-onlyIdempotent

List every source (web, scholar, news …), preset bundle, and inference model available. Returns sources (id, label, free flag), presets (id, included sources), and models (model id, provider, context window). Call once to discover valid values for the sources and model parameters of scout_quote and scout_answer.

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": "scout_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, and openWorldHint=false already declared, the description still adds real value by spelling out the return payload shape — sources with id/label/free flag, presets with included sources, and models with model id, provider, and context window — which is important since no output schema exists. It does not mention pagination, caching, or whether the catalog changes over time, keeping it short of 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?

Two sentences, both front-loaded: the first states what is listed, the second states what is returned and why to call it. No filler or redundancy.

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 zero-parameter, read-only catalog tool with no output schema, the description covers what is returned, at what granularity, and the intended downstream use — everything an agent needs to invoke it correctly.

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?

There are zero input parameters, so the baseline is 4 and nothing needs documenting on the input side; the description instead explains that the returned identifiers become the values for the sources and model parameters of sibling tools, which is a useful semantic bridge.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource set — 'List every source (web, scholar, news …), preset bundle, and inference model available' — and immediately enumerates the three returned collections, so an agent knows exactly what this tool yields without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states the calling pattern ('Call once to discover valid values for the sources and model parameters of scout_quote and scout_answer'), naming the two sibling tools whose parameters depend on this catalog and implicitly distinguishing this discovery step from the actual quoting/answering calls.

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.