Skip to main content
Glama

Fox River Press

Who reads these sites

network_readership
Read-onlyIdempotent

The last 30 days of self-identifying machine readership across the network: answers an AI assistant read a page for, pages read by AI crawlers and by search crawlers, and readers who arrived from an AI product, per site. Counts only; nothing about any reader is stored.

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

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 establish readOnly, idempotent, non-destructive, closed-world behavior. The description adds context annotations cannot carry: the window is fixed at the last 30 days, the figures are counts only, coverage is limited to 'self-identifying' machine traffic, and no reader-level data is stored. The 'self-identifying' qualifier is an important methodology caveat about what the counts do and do not include.

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 sentence that front-loads the time window and scope, then uses a colon-list for the measured categories and closes with the privacy note. Dense but well-structured; every clause carries information. The category list is slightly long but is the core of what the tool returns.

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?

With no parameters and no output schema, the description carries the burden of explaining the result, and it does so by enumerating the reported categories and the per-site granularity. Minor gaps remain: it does not say whether a network total is included alongside per-site rows, or whether site identifiers match those from list_sites.

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 zero parameters, so there is no parameter meaning for the description to supply and no risk of undocumented inputs. The schema is empty with additionalProperties false, consistent with the description's network-wide, fixed-window framing.

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 precisely (machine readership across the network, per site) and enumerates the measured categories — AI assistant answers, AI crawler pages, search crawler pages, AI-product referrals — over a fixed 30-day window. That is far more specific than the title 'Who reads these sites'. It does not explicitly name a sibling tool it replaces or defers to, which keeps it 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?

Usage is implied rather than stated: the fixed 30-day window and 'per site' scope tell an agent this is a network-wide aggregate report, not a single-site lookup. There is no explicit 'use this when…' framing and no pointer to a sibling for a different granularity or time range, so an agent must infer the boundary.

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