Skip to main content
Glama

Niche of One Network

Search archive

search_archive
Read-onlyIdempotent

Members only. Search the nicheof.one members archive (older issues and Sunday issues) by plain query terms. Needs a Backchannel sign-in.

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": {
      "query": "<query>"
    },
    "name": "search_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
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

A3.6/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower; the description still adds genuinely non-structured information — a membership restriction and an authentication requirement via Backchannel sign-in. It does not mention result limits or that the archive is a fixed corpus, but the auth disclosure is real added value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the access gate before the operation. The two access clauses ('Members only' and 'Needs a Backchannel sign-in') overlap somewhat, so a small amount of text does not earn its place.

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-only tool with no output schema, the definition covers access requirements and query semantics but leaves open how many results come back by default, what the limit does, and roughly what a result contains. Adequate to invoke, not complete enough to predict the response.

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 only 33%, with just 'offers' documented in the schema, so the description carries weight for the other two. 'Plain query terms' usefully implies no operators or advanced syntax for the required query parameter, but 'limit' (capped at 5) is left entirely unexplained, so compensation is partial.

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 names a specific verb and a specific resource: searching the nicheof.one members archive, further narrowed to 'older issues and Sunday issues', by plain query terms. That scope distinguishes it reasonably well from broader siblings such as search_site or onesearch, though it never names those alternatives explicitly.

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?

Access preconditions are stated clearly ('Members only', 'Needs a Backchannel sign-in'), which tells the agent when the call will fail, but there is no guidance on when to prefer this over search_site, onesearch, or get_archive_issue. Usage is implied by the archive scope rather than stated as a routing rule.

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