WarmInboxes Free MCP: Fleet Planner

Read a guide or study

read_resource

Read-onlyIdempotent

Read a WarmInboxes operator note, guide, study, playbook, dataset, recipe, comparison or changelog entry in full, as markdown. Long pages come in parts split at headings: the first call says how many, and nextPart gives the one to ask for. Datasets also return their data as JSON. Use the url find_resources gave you.

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": {
      "url": "<url>"
    },
    "name": "read_resource"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The page, as find_resources returned it, e.g. "https://warminboxes.com/research/inbox-placement-log", or a note as "note:<id>". A path works too.
`part`	No	Which part of a long page, from 1. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description rightly spends its words elsewhere: it discloses pagination behavior ("the first call says how many, and nextPart gives the one to ask for") and that datasets additionally return JSON. The reference to "nextPart" does not match the schema's "part" parameter name, a small ambiguity for an agent deciding what to pass.

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?

Four compact sentences, front-loaded with the core action and immediately followed by the operating constraint and the pagination rule. The middle sentence about parts is slightly tangled ("nextPart gives the one to ask for") but no sentence is filler.

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 two-parameter read tool with full schema coverage and no output schema, the description covers the action, the input provenance, the return format (markdown, plus JSON for datasets), and the pagination contract. What is missing is failure behavior for a bad or unrecognized url, which an agent would benefit from knowing.

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%, so both url and part are already documented in the schema, establishing a baseline of 3. The description reinforces the part semantics (splits at headings, count reported on first call) but adds no format or edge-case detail beyond what the schema states.

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+resource ("Read a ... operator note, guide, study, playbook, dataset...") and enumerates the content types covered. It is clearly differentiated from find_resources, which is named as the tool that supplies the url.

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

Usage Guidelines4/5

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

It states the prerequisite explicitly ("Use the url find_resources gave you") and explains when to use the part parameter (long pages split at headings). It does not state any when-not-to-use condition or what to do if a url is stale or invalid, which keeps it from a 5.

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

All WarmInboxes Free MCP: Fleet Planner 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?