Skip to main content
Glama

Niche of One Network

Read archive issue

get_archive_issue
Read-onlyIdempotent

Members only. Read one nicheof.one members archive issue by the slug search_archive returns. 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": {
      "slug": "<slug>"
    },
    "name": "get_archive_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
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

A4/5.0
Behavior4/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 the access requirements (membership plus Backchannel sign-in) that annotations cannot express. It says nothing about what happens with an unknown or malformed slug, which is the main remaining behavioral gap.

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?

Three short sentences, zero filler, with the access restriction and the slug-source rule front-loaded. Every sentence carries distinct information.

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

Completeness4/5

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

For a simple, idempotent read with no output schema, the description covers access, prerequisites, and the key input's origin. What an issue contains and how an invalid slug is reported are left implicit, which is a minor but real omission.

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 coverage is 50%: the slug pattern/length and the full behavior of 'offers' are already documented in the schema. The description's one real addition is provenance for slug (it comes from search_archive), which is genuinely useful but limited. It adds nothing about the optional 'offers' flag beyond what the schema already says.

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?

States a specific verb and resource ('Read one nicheof.one members archive issue') and ties the input to its source ('by the slug search_archive returns'), which distinguishes it from the search sibling. It does not explicitly distinguish itself from other single-item readers like sunday_issue or todays_issue, so it stops 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 Guidelines4/5

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

Gives the prerequisite workflow directly: obtain the slug from search_archive, then call this tool. It also states access conditions ('Members only', 'Needs a Backchannel sign-in'). No explicit when-not or failure-mode guidance is given, so no 5.

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