CamFeed Journalism Archive

Recommended reading

recommended_reading

Read-onlyIdempotent

Use this when someone wants a short, curated reading list of Cameron Wilson's work on a topic. Do not use it for exhaustive archive enumeration.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "recommended_reading"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`topic`	Yes

Output Schema

Name	Required	Description	Default
`topic`	No
`reading_list`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that the output is curated and short, and that exhaustive enumeration is not the intended use, which complements the annotation without contradicting them.

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 concise sentences, front-loaded with the primary use case and an explicit exclusion. No unnecessary detail.

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 read-only recommendation tool with an output schema, the description covers purpose and usage boundaries. However, the lack of parameter semantics is a minor gap given the 0% schema coverage, so it is not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description should explain parameters. It does not mention 'topic' or 'limit' at all, leaving the agent to infer their meanings. The schema provides a default and bounds for limit, but no semantic context is given.

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 clearly states the tool's purpose: providing a short, curated reading list of Cameron Wilson's work on a topic. It also distinguishes itself from exhaustive archive enumeration, differentiating it from sibling search tools.

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?

Explicitly states when to use ('when someone wants a short, curated reading list') and when not to use ('Do not use it for exhaustive archive enumeration'), giving clear guidance relative to alternatives.

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

All CamFeed Journalism Archive tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?