Skip to main content
Glama

Niche of One Network

Network map

network_map
Read-onlyIdempotent

The Codex: how the Niche of One network fits together (rooms, guides, fiction, radio, characters) and what connects to what.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoA node id or label; returns what connects to it.
typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is fully covered and the description is not obliged to restate it. What the description adds is the content scope (rooms, guides, fiction, radio, characters), which is useful context not present in the annotations. It adds nothing operational beyond that — no indication of what is returned for a node, how deep the connections go, or how large the map can be.

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 sentence with no filler; the leading 'The Codex:' label front-loads the domain name and the rest scopes the contents. It is efficient, though the colon-joined framing is slightly less scannable than a plain verb-first statement would be.

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

Completeness3/5

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

With no output schema and zero required parameters, the description carries the burden of explaining what a bare call returns (the whole map? an index?) and what a connections result looks like — neither is addressed. For a simple two-optional-parameter lookup the gap is not severe, but it leaves the agent guessing at the shape of the response before the first call.

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 'node' parameter is documented in the schema ('a node id or label; returns what connects to it') and the description aligns with that by framing the tool as 'what connects to what'. The 'type' parameter is undocumented in both places — no enum, no example values — although the parenthetical list (rooms, guides, fiction, radio, characters) hints at plausible node categories without formally mapping them to the 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?

The description conveys the resource — a map of how the Codex network's rooms, guides, fiction, radio and characters connect — but there is no explicit verb or return statement; 'how X fits together' is a conceptual framing rather than a stated operation. It does not distinguish itself from siblings such as radio_now, radio_schedule, get_page or onesearch, which cover overlapping content domains, so an agent cannot tell without opening the schema that this one returns relationships rather than content.

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, no prerequisite, and no named alternative. An agent reading the sibling list cannot infer whether to call network_map first for orientation or to go straight to get_page/radio_now for actual content; nothing in the text resolves that choice.

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