Skip to main content
Glama

Niche of One Network

Shows

shows_browse
Read-onlyIdempotent

The network's audio shows and their episodes: titles, dates, descriptions and audio links.

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

Input Schema

NameRequiredDescriptionDefault
showNo
episodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without the description. Beyond that, the description adds only a list of returned fields and says nothing about pagination, result ordering, whether unfiltered calls return all shows, or how the show/episode parameters narrow results.

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 short sentence with no padding, so nothing is wasteful. But it is a sentence fragment with a colon list rather than a front-loaded statement of action and scope, and its brevity comes at the cost of under-specification.

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?

With two undocumented parameters, no output schema, and no annotations needing supplementation, the description carries the full burden of explaining behavior — and it only describes the payload's fields. An agent knows the topic but not how to invoke the tool or what a filtered versus unfiltered call returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description never mentions the 'show' (string, max 80) or 'episode' (integer, 1-1000) parameters. It does not say whether they are filters, identifiers, or lookups, nor what happens when they are omitted — leaving both parameters semantically undefined.

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 ('the network's audio shows and their episodes') and enumerates the payload fields (titles, dates, descriptions, audio links), so the subject matter is clear. However it is a noun-phrase fragment with no verb, so it never states whether the tool lists, browses, or fetches, and it gives no hint about how it differs from siblings such as radio_schedule or now_playing.

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 preconditions, and no mention of any alternative tool. An agent must infer from the name alone that this is the browse entry point for show/episode content.

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