Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

get_video

Read-onlyIdempotent

Get a Canton Network video that CCPEDIA has cached (curated channels: Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml) by its YouTube id: title, channel, publish date, description and full transcript text if stored. CANTON-ONLY and limited to videos already in CCPEDIA's index. Does NOT fetch arbitrary YouTube videos (use a dedicated YouTube tool for that). Obtain ids from list_videos or search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesYouTube video id, e.g. "dQw4w9WgXcQ"
transcript_charsNoTranscript characters to return. Default 12000; raise it (max 200000) for the full text, or set 0 for metadata only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / transcript_chars
      Added value: +{
+  "default": 12000,
+  "description": "Transcript characters to return. Default 12000; raise it (max 200000) for the full text, or set 0 for metadata only.",
+  "maximum": 200000,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds useful context beyond those: the closed-world limitation to cached/curated channels, conditional transcript availability ('if stored'), and a clear statement that arbitrary videos are not fetched. No contradiction with annotations.

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?

Three sentences, each earning its place: the first states purpose and return fields, the second scopes the tool, and the third gives sourcing guidance. It is front-loaded and free of redundancy.

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?

For a read-only get-by-id tool with one required and one optional parameter, the description covers the return values, scope limitations, and sources for valid ids. The schema covers parameter mechanics, and the lack of an output schema is acceptable because the description enumerates the response contents. Complete for its complexity.

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?

The input schema already fully describes both parameters (id string with example, transcript_chars with default/min/max and purpose). The description adds only a high-level mention of 'full transcript text if stored', so it does not need to compensate for schema gaps. A baseline of 3 is appropriate given 100% schema coverage.

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 opens with a specific verb ('Get') and a clearly defined resource ('a Canton Network video ... by its YouTube id'), and enumerates the exact return fields (title, channel, publish date, description, transcript). It also distinguishes the tool from arbitrary YouTube fetching by restricting to CCPEDIA's curated index.

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

Usage Guidelines5/5

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

Explicitly states the scope ('CANTON-ONLY', 'limited to videos already in CCPEDIA's index'), the exclusion ('Does NOT fetch arbitrary YouTube videos'), and directs users to dedicated tools and id sources ('Obtain ids from list_videos or search'). This gives clear when-to-use and when-to-avoid guidance.

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