Skip to main content
Glama

Niche of One Network

Quote

quote
Read-onlyIdempotent

Quote an exact published passage from NoO Network, with attribution and canonical URL; at most 80 words.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
siteNoniche-of-one
sectionNo
maxWordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavior context: the 80-word limit and the fact that results include attribution and a canonical URL. It still does not explain what happens for invalid URLs, missing sections, or passages that exceed the word limit, so it adds only moderate transparency 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?

The definition is a single front-loaded sentence that states the action, output requirements, and word limit without filler. The semicolon cleanly separates the core action from the constraint, and every phrase contributes information. There is no unnecessary wording.

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

Completeness2/5

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

There is no output schema, and the input schema has four parameters with zero description coverage. The description gives the core action and word limit but does not explain site, section, URL expectations, or error behavior. Annotations cover the safety profile, but the definition remains incomplete for reliably invoking the tool across its parameters.

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 0%, so the description must carry parameter meaning. It only loosely connects to "url" via "canonical URL" and to "maxWords" via the 80-word limit; it says nothing about the "site" enum, the "section" parameter, or how url, site, and section relate. With four parameters and no schema descriptions, this is insufficient compensation.

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?

The description uses a specific verb, "Quote," and names the resource and scope: an exact published passage from NoO Network. It also states the required attribution and canonical URL plus the 80-word ceiling, making the operation clear. It does not explicitly distinguish this tool from likely siblings such as get_page or read_serial, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description explains what the tool does but gives no when-to-use or when-not-to-use guidance. It does not mention alternatives like get_page or read_serial, nor does it state prerequisites such as whether the URL must point to a NoO Network page. Usage is only implied by the phrase "exact published passage."

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