Skip to main content
Glama

Niche of One Network

Roster

roster
Read-onlyIdempotent

The Niche of One roster: staff, bands and cast, with roles and short bios.

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

Input Schema

NameRequiredDescriptionDefault
qNoA name or word to look for.
groupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive behavior, so the safety profile is covered. The description adds only content categories (staff, bands, cast, roles, bios) and says nothing about filtering behavior, result shape, pagination, or how the parameters affect output. That is minimal behavioral disclosure beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, but it is a fragment that omits the verb and any operational guidance. Brevity here reflects under-specification rather than disciplined structure, so it earns only a moderate score.

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 read-only browse/search tool with no output schema, the description should at least clarify what q searches and what group filters by, plus what the response contains. It gives content categories but leaves the core filter semantics and return behavior unstated. This is not complete enough for reliable invocation.

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?

The input schema documents q as 'A name or word to look for' but leaves group entirely undescribed at 50% schema coverage. The description does not mention q or group at all, so it adds no meaning beyond the schema and fails to compensate for the undocumented group parameter. An agent cannot tell whether group means staff/band/cast category or something else.

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 names the resource and its contents ('staff, bands and cast, with roles and short bios'), but it supplies no action verb such as list, search, or get. An agent can infer a roster lookup, but the purpose remains a noun-phrase description rather than a specific operation.

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 exclusions, and no mention of alternatives among siblings such as academy_browse or onesearch. The agent gets no signal about whether this is for browsing the full roster or searching/filtering it.

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