Get a token-cheap table of contents for a URL: every heading plus the approximate token cost of its section. Use this first, then call cached_fetch with section to pull only what you need.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description mentions 'token-cheap' hinting at low cost but lacks details on caching, rate limits, or side effects. Adequate but not comprehensive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose, no superfluous text. Highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one param and no output schema, description covers purpose, usage, and relationship to sibling. Lacks exact output format but adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and description adds no information about the 'url' parameter beyond schema definition (type string, format uri). Description fails to compensate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb 'Get', resource 'table of contents', and distinguishes from sibling 'cached_fetch' by specifying it provides headings with token costs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises to use this tool first before 'cached_fetch' with section parameter, providing clear usage order and alternative.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, distinct purpose: fetching cached content, getting outlines, leaving/recalling notes, flagging/voting notes, global stats, and cutoff-aware updates. No overlapping functionality.
Two naming prefixes are used ('cached_' and 'slipstream_'), plus 'whats_new' deviates entirely. While 'slipstream_' is consistent for most tools, the mixture with 'cached_' and the odd 'whats_new' reduces overall consistency.
8 tools cover the server's domain well—neither too few nor too many. Each tool earns its place for a focused collective caching and note-taking service.
The tool set covers core operations: fetch/outline (read), note creation, recall (read notes), flag/vote (moderation), and whats_new (diff). Missing explicit update or delete for notes, but flagging serves as a community-driven delete mechanism.