Skip to main content
Glama

Niche of One Network

My brief

my_brief
Read-onlyIdempotent

Members. A short sectioned brief, like a mini paper: what is new on the Niche of One network and from the archive, matched to the interests you set. Long text: best shown to the user as a document or artifact.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoStart date as YYYY-MM-DD. Leave it out for the last seven days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 closed-world scope, so the safety profile is covered. The description adds value beyond that: a membership requirement and, importantly, that output is long text best surfaced to the user as a document or artifact — a rendering instruction the agent would otherwise not know.

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, each carrying distinct information: audience gate, content composition, and output-format guidance. The terse 'Members.' opener is slightly abrupt but front-loads the access condition efficiently; 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 read-only tool with one optional parameter and no output schema, the description supplies the essentials: what the brief contains, who can call it, and how to present the long result. It does not address empty/insufficient-content cases or how sections are organized, which are minor gaps for a tool at this complexity.

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 100% and the single 'since' parameter is fully documented in the schema, including its YYYY-MM-DD format and seven-day default, so baseline 3 applies. The description gestures at recency ('what is new') but does not restate or extend the date-window semantics.

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 concrete deliverable (a short, sectioned brief of what is new on the Niche of One network plus archive items, matched to the user's interests), which is specific enough to distinguish it from sibling readers like my_library or read_serial. It lacks an explicit verb such as 'generate' or 'fetch', so the action is implied rather than stated, but the resource and its scope are unmistakable.

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?

The opening 'Members.' establishes a membership precondition, which is useful gating information. However, there is no explicit when-to-use framing versus alternatives (e.g. my_library, read_serial, onesearch) and no when-not guidance, so the agent must infer that this is the personalized-digest path.

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