Skip to main content
Glama

Niche of One Network

Issue

todays_issue
Read-onlyIdempotent

Read the newest dated NoO Network entries and their publication date.

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

Input Schema

NameRequiredDescriptionDefault
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

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are the newest dated entries and include a publication date, which is useful return-shape context, but it says nothing about result count, ordering across sites, or what happens when no entry exists for the default site.

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?

A single efficient sentence with no filler, and the key scope word 'newest' is front-loaded. It is slightly under-specified rather than bloated, so it loses a point only for what it omits, not for wasted 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?

For a two-parameter tool with no output schema and an undocumented site enum, the description should explain the site dimension and what 'entries' look like. As written it leaves the agent guessing which site it will read and how many items come back, which is inadequate given the schema gap.

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 coverage is only 50%: the site parameter has an enum but no description, and the description never mentions site selection, its default of "niche-of-one", or what the eight site values mean. The offers parameter is documented in the schema itself, so the description adds essentially nothing beyond the schema on either parameter.

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

Purpose3/5

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

"Read the newest dated NoO Network entries and their publication date" gives a verb and a resource, but "NoO Network entries" is undefined jargon and the scope (how many entries, per-site or across sites) is vague. It does not distinguish itself from siblings such as get_archive_issue or sunday_issue, so an agent cannot tell which issue tool to pick from the description alone.

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?

There is no when-to-use guidance at all — nothing says to reach for this instead of get_archive_issue or sunday_issue, and no condition for the offers parameter is given in the description. The only 'when' hints ('newest dated') are implied by the word newest rather than stated as guidance.

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