Skip to main content
Glama

Canon Person Get

canon_person_get
Read-onlyIdempotent

What one person has actually said across podcasts, per CanonCannon, their appearances by show and the ideas attributed to them, drawn from 3,800+ people in the corpus. Answers "does this person keep making this claim, and where" rather than "who is this person". Requires a CanonCannon API key via _apiKey. Example: canon_person_get({ slug: "peter-attia" }).

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": "peter-attia"
    },
    "name": "canon_person_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCanonCannon person slug, from canon_search or canon_episode_get.
_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 the safety profile is covered. The description adds real context beyond them: the auth requirement via _apiKey, the 3,800+ person corpus scope, and a sketch of the return contents. It does not mention pagination, result size limits, or behavior for unknown slugs, which keeps it below 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?

Four compact sentences with no filler, and the corpus-size detail earns its place by conveying coverage. It opens with a long noun clause rather than the verb, so the core action is slightly delayed, but nothing is redundant enough to penalize further.

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 results and it does so concretely — show-by-show appearances and attributed ideas — while also covering auth and giving a call example. For a two-parameter read tool, an agent has everything needed to call it correctly.

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% and the schema already documents slug provenance (from canon_search or canon_episode_get) and the cc_live_ key format. The inline example call repeats the slug example already present in the schema's examples array, so the description adds little new parameter meaning. Baseline 3 is appropriate.

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 resource (one person's podcast statements) and enumerates what is returned: appearances by show and ideas attributed to them. It also draws an explicit boundary against a different kind of lookup ("does this person keep making this claim, and where" rather than "who is this person"), so an agent can distinguish it from a generic entity-profile tool without opening the schema.

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?

It gives a clear use case framed as a question the tool answers, plus the contrasting question it does not answer, which is genuine routing guidance. It also states the API-key prerequisite up front. There is no explicit named alternative (e.g., pointing to canon_search for slug discovery), so it falls short of a 5.

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.