Skip to main content
Glama

Canon Get

canon_get
Read-onlyIdempotent

The full CanonCannon entry for one idea, the claim, the evidence behind it, the nuance and gaps, related entries and books, alongside its measurement (independent podcast count, independent speaker count, the bar in force, and when it was last verified). Get the slug from canon_search. Requires a CanonCannon API key via _apiKey. Example: canon_get({ slug: "circadian-rhythm-health-foundation" }).

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": {
      "slug": "circadian-rhythm-health-foundation"
    },
    "name": "canon_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCanonCannon canon slug, from canon_search.
_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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds meaningful context beyond them: a mandatory CanonCannon API key passed via _apiKey, and the exact shape of the returned payload (content sections plus measurement metrics and last-verified timestamp). It does not mention rate limits or error behavior, which keeps it short of a 5.

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?

The payload contents are front-loaded in the first sentence, followed by the prerequisite and auth note in short order. The opening sentence is a dense comma-heavy list, but every element maps to a real return field rather than filler.

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

Completeness5/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 carries the burden of describing return values and does so concretely (claim, evidence, nuance/gaps, related entries and books, measurement counts, verification date). Auth, prerequisite, and identifier format are all covered, leaving nothing essential for a correct call unstated.

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 100%; both slug and _apiKey are already documented in the schema, including the cc_live_ key format. The description reinforces the slug's provenance (from canon_search) and gives a worked call example, but that example largely duplicates the schema's examples field, so added meaning is marginal beyond baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific retrieval ("The full CanonCannon entry for one idea") and then enumerates exactly what that entry contains: claim, evidence, nuance and gaps, related entries and books, and measurement fields. It also explicitly contrasts this with canon_search (which supplies the slug), so an agent can distinguish lookup-by-slug from discovery.

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?

"Get the slug from canon_search" establishes a clear workflow prerequisite: search first, then fetch details here. It does not state an explicit when-not-to-use case or name other detail-fetching siblings (canon_person_get, canon_podcast_get), but the required-input routing is unambiguous for this tool.

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.