Skip to main content
Glama

Canon Corpus Stats

canon_corpus_stats
Read-onlyIdempotent

CanonCannon corpus size and the canon bar CURRENTLY in force, entry, episode, idea and person counts, the tracked-podcast count, and the independent-podcast threshold an idea must clear. Call this to state the standard you are quoting: the bar is ceil(5% of tracked podcasts), so it rises as the corpus grows. Requires a CanonCannon API key via _apiKey. Example: canon_corpus_stats({}).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "canon_corpus_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyNoCanonCannon API key (cc_live_...). Every /api/v1 endpoint refuses without it. Keys are issued by CanonCannon, https://canoncannon.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"CanonCannon API key (cc_live_...). Every /api/v1 endpoint refuses without it. Keys are issued by CanonCannon — https://canoncannon.com"New value: +"CanonCannon API key (cc_live_...). Every /api/v1 endpoint refuses without it. Keys are issued by CanonCannon, https://canoncannon.com"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the threshold is computed as ceil(5% of tracked podcasts) and moves as the corpus grows, plus the API-key gate. It does not discuss caching or freshness of the counts, which keeps it at 4.

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?

Front-loaded and dense with no filler; the formula and the example call are both load-bearing for an agent deciding whether to invoke it. The first sentence is an awkward run-on list missing a leading verb, which costs a point but does not obscure the content.

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?

There is no output schema, so the description must describe return values, and it does so by enumerating every reported count plus the threshold. Combined with the computation rule for the bar, an agent can report results correctly without further documentation; only count freshness/timing is unaddressed.

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?

With one parameter at 100% schema coverage, the schema already documents _apiKey fully. The description restates the requirement ("Requires a CanonCannon API key via _apiKey") without adding format or acquisition detail beyond what the schema says, so it sits at the baseline.

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?

It enumerates exactly what the tool returns: corpus entry/episode/idea/person counts, tracked-podcast count, and the independent-podcast threshold. This is clearly an aggregate-stats tool rather than a per-entity lookup, which implicitly separates it from siblings like canon_podcast_get and canon_episode_get. It loses a point only because the opening is a noun-phrase list with no explicit verb framing the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call this to state the standard you are quoting" gives a concrete situation for invoking it, and the follow-on explains why the figure is dynamic (the bar rises as the corpus grows). There is no explicit when-not or named alternative, but given it is the only corpus-level stats tool among entity-scoped siblings, the context is sufficient.

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.