Skip to main content
Glama

Niche of One Network

New

whats_new
Read-onlyIdempotent

List everything NoO Network published since a date, newest first: title, date, one-line summary and link. Defaults to the last seven days.

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

Input Schema

NameRequiredDescriptionDefault
siteNoOne site. Leave it out to cover every site in the network.
limitNo
sinceNoISO date, YYYY-MM-DD. Defaults to seven days ago.
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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds useful context beyond them: result ordering ('newest first'), the exact fields returned, and the default time window. It stops short of describing pagination or what happens when limit is hit.

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?

Two tight sentences with the core behavior and default front-loaded, followed by the return shape. Nothing is redundant or padded.

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?

With no output schema, the description usefully names the returned fields and the ordering, which is the main thing an agent needs. Coverage of the limit parameter and any result-count behavior is the remaining gap for a simple four-parameter read tool.

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 75%: site, since, and offers are already documented in the schema, and the description mostly restates the seven-day default for since. The limit parameter carries no schema description and the description does not compensate, so the baseline of 3 for high coverage is appropriate.

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 ('List everything NoO Network published since a date') and even enumerates the returned fields (title, date, summary, link), so an agent knows exactly what it gets back. It does not explicitly contrast itself with feed-like siblings such as get_page or onesearch, so it falls just short of the top score.

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?

Usage context is implied rather than stated: 'Defaults to the last seven days' and the offers parameter note ('for when the user asks for recommendations') give partial triggers. There is no explicit when-not guidance or named alternative for retrieving a single item versus browsing a feed.

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