Skip to main content
Glama

Niche of One Network

Read

get_page
Read-onlyIdempotent

Read a NoO Network corpus page by exact canonical URL. Index-only entries contain published summaries.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
siteNoniche-of-one
offersNoDefault false. true adds one related item from our shop after the result, for when the user asks for recommendations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine beyond-schema context that index-only entries return published summaries rather than full text, but it says nothing about failure behavior for non-canonical URLs, redirects, or whether full entries differ in shape.

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 short sentences with zero filler; the lookup key and the one notable content caveat are both front-loaded.

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

Completeness3/5

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

For a three-parameter read tool with no output schema and rich annotations, the description covers the core access model and one content caveat. It leaves the site parameter's semantics and error/edge behavior unexplained, which is a meaningful gap given the low schema coverage.

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 only 33%: offers is documented in the schema, the site enum lists values but never explains what it does or when the niche-of-one default is wrong. The description clarifies the url parameter as an exact canonical URL but never mentions site at all, so the agent gets no guidance on a parameter that likely affects which page resolves.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read a NoO Network corpus page by exact canonical URL" gives a specific verb (read), a bounded resource (a corpus page) and the lookup key (exact canonical URL), which distinguishes it from likely siblings like read_serial or read_library that are not URL-driven. It stops short of explicitly naming which sibling to use for non-URL lookups, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

The phrase "by exact canonical URL" implies this tool is only for direct URL retrieval and not discovery or search, and the index-only note sets expectations for partial-content pages. However, there is no explicit when-to-use versus alternatives, no exclusion (e.g. what to do when the exact URL is unknown), and no mention of the site parameter's role in routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources