Skip to main content
Glama
Sign In

Tollkit

by io.github.UltraStarz
OverviewDiscussionsAdmin

Page brief

page_brief
Read-only

Read any web page in a real browser and get a summary of it in one call, with its title and final URL. Says when the page was longer than the part summarized.

$0.007 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote.

When to use: You need the gist of one page, not its full text. Use instead: read_page for the full text; read_pages for several pages. Parameters: url: absolute https URL. max_words: summary length, 10-250, default 60. Returns: summary, title, final_url, and a note when the page was longer than the part summarized.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute https URL of the page.
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.
max_wordsNoSummary length in words (default 60).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld, but the description adds the critical unseen behavior: per-call cost ($0.007 USDC over x402), that failed calls are free, and the two-step payment flow (call without `payment` to get a quote, then sign). It also discloses truncation behavior ('says when the page was longer than the part summarized'). This is substantial context beyond the annotations.

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?

Front-loaded purpose sentence, then labeled blocks (pricing, When to use, Use instead, Parameters, Returns). Dense but every line carries distinct information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description enumerates the return fields (summary, title, final_url, truncation note). Combined with the payment flow, parameter range, and sibling routing, an agent has everything needed to invoke it correctly.

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 the schema already documents url, payment, and max_words including the range and default. The description largely restates those facts, adding only mild emphasis on the quote flow. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Read any web page in a real browser and get a summary'), plus the concrete outputs (title, final URL). Explicitly names sibling tools it is not (read_page, read_pages), so an agent can distinguish it without opening schemas.

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?

Gives an explicit condition ('You need the gist of one page, not its full text') and names the alternatives with their selecting conditions ('read_page for the full text; read_pages for several pages'). No inference required.

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

All Tollkit toolsInspect
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