NestDaddy

read_page

Read-onlyIdempotent

Read the full text of one web page or news article (title, author, date and the main text, without menus or ads). Use it after news or web_search when you need the details behind a headline. url: the page link from a search or news result. max_chars: 500-30000 (default 8000).

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Full http(s) link of the page, usually from a search or news result.
`max_chars`	No	Most characters of text to return, 500-30000.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026

addedInput schema / properties / max_chars / description

Added value: +"Most characters of text to return, 500-30000."

addedInput schema / properties / url / description

Added value: +"Full http(s) link of the page, usually from a search or news result."

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the returned payload excludes navigation and ads, and output length is bounded by max_chars. It omits realistic failure modes for a fetch tool (paywalls, bot-blocked or JS-rendered pages), which keeps 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?

Three sentences: purpose and payload first, then the routing rule to sibling tools, then the two parameters. Nothing is redundant and the most decision-relevant information is front-loaded.

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 an output schema present and only two simple parameters, the description covers everything needed to invoke it correctly. The only gap is unstated limits on what pages it can actually retrieve, which matters for an open-world fetch tool.

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 parameters are already documented with the same details the description provides ('full http(s) link' and '500-30000, default 8000'). The description adds no usage nuance beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ('Read the full text of one web page or news article') and enumerates exactly what comes back (title, author, date, main text, no menus or ads). This is clearly distinct from search-oriented siblings like web_search and news, which return listings rather than page bodies.

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 triggering condition explicitly: use it after news or web_search when you need the details behind a headline. That names the sibling tools and the follow-up workflow, though it does not say when NOT to use it (e.g., when a snippet already suffices).

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

All NestDaddy 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.