Skip to main content
Glama

Band stats

band_stats

Retrieve a quick overview of total songs, setlists, shows, and upcoming show counts to summarize band activity at a glance.

Instructions

Quick overview: total songs, setlists, shows, and how many shows are coming up.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about this being a read-only, side-effect-free operation, about permission or auth requirements, or about data freshness. It does disclose the metric set, which partially compensates since there is no output schema, but the behavioral profile is essentially undisclosed.

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?

A single short sentence that front-loads the overview framing and lists the metrics in a scannable order. 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 does the right thing by enumerating the returned aggregates, and a zero-parameter tool is simple enough that little else is needed. It stops short of clarifying how 'coming up' is defined (time window, timezone) or the shape of the counts, which an agent would have to discover at runtime.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. No misleading parameter claims are made.

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 the resource (band stats) and enumerates exactly which aggregates are returned: total songs, setlists, shows, and upcoming show count. That distinguishes it implicitly from siblings like list_songs and list_shows, which return records rather than totals, though no verb such as 'get' or 'compute' anchors the purpose explicitly.

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?

'Quick overview' hints at using this for summary questions instead of per-record tools, but the description never states when to choose this over list_shows or get_show, nor any exclusions. The usage cue is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.