Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

search_talks

Read-onlyIdempotent

Search CCPEDIA's indexed Canton talks/videos (YouTube transcripts). Canton-specific. Returns matches across title + transcript with the best-matching passage, its time in the video and a link that opens the video there.

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 5).
queryYesFree-text query. Appears in title or transcript.
offsetNoSkip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / maxLength
      Added value: +200
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Free-text query — appears in title or transcript."New value: +"Free-text query. Appears in title or transcript."
  5. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description earns credit for disclosing the response shape beyond annotations: best-matching passage, its timestamp in the video, and a deep link that opens there. It does not say whether matching is keyword or semantic, which matters for query phrasing.

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?

Three tight sentences with the capability statement front-loaded and the return value last. 'Canton-specific' is mildly redundant next to 'Canton talks/videos' but does reinforce scope.

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 carries the return-value explanation and does so adequately, including the deep-link behavior. What remains unstated is index freshness/coverage and whether results are ranked by relevance, which would matter for interpreting matches and paging.

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%, so query/limit/offset are already fully documented with bounds and defaults. The description adds only that the query matches title + transcript, which is modest added meaning over the schema's 'Appears in title or transcript' wording.

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?

Names a specific verb (search) and a specific resource (CCPEDIA's indexed Canton talks/YouTube transcripts), plus the match surface (title + transcript). An agent can tell this is video-content search rather than a general knowledge search, though it never names the nearest siblings (get_video, list_videos, semantic_search) to sharpen the boundary.

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 explicit when-to-use statement and no exclusions or alternatives. 'Canton-specific' is the only scoping cue, leaving the agent to infer that it should choose this over list_videos or semantic_search on its own.

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

All canton-ccpedia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources