Skip to main content
Glama

Niche of One Network

Sunday issue

sunday_issue
Read-onlyIdempotent

Members only. Read the newest members-only Sunday issue from nicheof.one, or an earlier one by number. Needs a Backchannel sign-in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sunday_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueNo
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.9/5.0
Behavior4/5

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

The annotations already declare this as a safe, idempotent, closed-world read, and the description usefully adds that access is members-only and requires a Backchannel sign-in. It does not describe failure behavior when unauthenticated or any rate or pagination details, but that is a minor gap given the annotation coverage.

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 with the access restriction front-loaded, then the core action and auth requirement. Every sentence adds information and there is no filler.

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 authenticated read tool with no output schema, the definition supplies the important access prerequisite, default behavior, and issue-selection semantics. The remaining detail, the offers recommendation flag, is adequately covered by the schema description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description covers the offers parameter, while the description supplies meaning for the otherwise undocumented issue parameter: omitting it reads the newest issue and supplying it reads an earlier issue by number. That adds useful semantics beyond the schema, though offers is left entirely to the schema.

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 ("Read") and resource ("newest members-only Sunday issue from nicheof.one"), and clarifies that an earlier issue may be selected by number. It is clear enough to distinguish from a generic issue reader, though it does not explicitly route the agent against siblings such as get_archive_issue or todays_issue.

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?

It establishes prerequisites (members-only, Backchannel sign-in) and explains the default newest-issue behavior versus selecting an earlier issue by number. However, it gives no explicit when-to-use guidance relative to sibling tools, nor any when-not conditions.

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