Skip to main content
Glama

Fox River Press

List the sites

list_sites
Read-onlyIdempotent

Every site Fox River Press publishes: what it is for, how its pages are made and checked, and what it holds.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 and determinism are covered. The description adds that the result is exhaustive ("Every site") and that entries carry purpose, build/check process, and contents — useful context about payload shape. It says nothing about pagination, ordering, or result size, which is the remaining behavioral gap.

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 identifying the resource first, then the entry contents — no boilerplate or repetition of the title. The trailing clauses ("how its pages are made and checked") are slightly evocative rather than precise, which costs a point.

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 zero-argument, read-only list tool with no output schema, the description supplies the essential facts: it returns all sites and roughly what each record describes. Return format and pagination are unspecified, but the tool's simplicity makes that a minor omission.

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; the baseline for a zero-param schema applies. The description correctly implies no filtering or arguments are needed to enumerate everything.

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?

"Every site Fox River Press publishes" names the resource and its scope (all sites, no filtering), and the following clauses hint at what each entry contains. The verb is implicit rather than stated (the title supplies "List"), but an agent can still tell this is an inventory read of the publisher's sites. It does not explicitly contrast itself with any sibling, though the siblings listed are clearly unrelated domains.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus anything else, no prerequisites, and no exclusions. Usage is only implied by the phrase "Every site ... publishes," which suggests a discovery/overview call. With zero parameters there is little to get wrong, but the agent receives no routing guidance.

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