Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

list_videos

Read-onlyIdempotent

List Canton Network videos cached in CCPEDIA, filtered by channel (Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml, Digital Asset Training), publish date (since), and transcript availability. CANTON-ONLY corpus. These are curated Canton ecosystem videos, not general YouTube. Returns metadata only (id, title, channel, date); call get_video with an id for the transcript.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many videos to return. Default 20, max 100.
sinceNoEarliest published_at (ISO date, e.g. "2026-01-01"). Default: no lower bound.
offsetNoSkip this many before returning, for paging past the limit. The response states the full count and echoes the offset used.
channelNoChannel name filter, one of Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml, Digital Asset Training. Case-insensitive substring.
has_transcriptNoIf true, only return videos with a stored transcript. If false, only those still missing one. Omit for both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / channel / description
      Previous value: -"Channel name filter, e.g. \"Canton Network\", \"Digital Asset\", \"Sync Insights\", \"Canton Foundation\", \"Daml\". Case-insensitive substring."New value: +"Channel name filter, one of Canton Network, Digital Asset, Sync Insights, Canton Foundation, Daml, Digital Asset Training. Case-insensitive substring."
  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. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many videos to return. Default 20, max 100."
    • addedInput schema / properties / offset / description
      Added value: +"Skip this many before returning, for paging past the limit. The response states the full count and echoes the offset used."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, openWorld=false), but the description adds genuinely new context: the corpus is a local cache restricted to Canton channels, and it enumerates the returned metadata fields (id, title, channel, date), which matters because there is no output schema. It stops short of describing paging/count behavior, which the offset param handles.

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 tight sentences: scope and filters first, corpus boundary second, return shape and next step last. No filler, and the most decision-relevant constraint (Canton-only) is front-loaded.

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 zero required params, no output schema, and full schema coverage, the description supplies exactly the missing pieces: what comes back, what doesn't (transcripts), and where to go next. Nothing an agent needs in order to call it correctly is absent.

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 every parameter is already documented with defaults, bounds, and matching semantics. The description's channel list and 'since'/'transcript availability' mention merely restate what the schema declares, adding no syntax or edge-case detail beyond it.

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?

Specific verb+resource ('List Canton Network videos cached in CCPEDIA') with the filtering dimensions named up front. It sharply differentiates from get_video (metadata vs transcript) and from any general YouTube tooling by declaring 'CANTON-ONLY corpus ... not general YouTube'.

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?

Explicit when-to-use (curated Canton ecosystem videos), when-not-to-use (general YouTube), and the alternative route for a different need ('call get_video with an id for the transcript'). An agent can decide between list_videos and get_video without inspecting either schema.

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