Skip to main content
Glama

canton-ccpedia

by io.github.UnityNodes
OverviewDiscussionsAdmin

get_doc

Read-onlyIdempotent

Fetch the FULL text of one indexed Canton-ecosystem documentation page (Canton/Daml/Splice and integrated partner docs) by its numeric id. Canton-specific. Use this AFTER search or semantic_search returns a doc id, to read complete commands, flags, and full sections a search snippet truncates. Requires an id. Not a discovery tool; use search/semantic_search first.

Input Schema

NameRequiredDescriptionDefault
idYesDoc page ID from a search/semantic_search result, e.g. 3242 or "doc:3242". Not a forum topic id: those go to get_discussion.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed5 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]
    • changedInput schema / properties / id / description
      Previous value: -"Doc page ID (from search/semantic_search results)"New value: +"Doc page ID from a search/semantic_search result, e.g. 3242 or \"doc:3242\". Not a forum topic id: those go to get_discussion."
    • removedInput schema / properties / id / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / id / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / id / type
      Removed value: -"integer"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by explaining that it returns the complete untruncated text versus a search snippet, and that an id is mandatory. It does not mention behavior on an invalid or stale id, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the verb and resource, then the precondition, then the exclusion. Nothing is redundant, and the most decision-relevant constraint (use after search) appears early.

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 one required parameter, rich annotations, and no output schema, the description covers what an agent needs: what is returned (full text), the domain scope, and the prerequisite. It omits only edge behavior such as errors for invalid ids or size limits on large pages.

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 description coverage is 100%, and the schema itself documents both accepted forms (3242 or "doc:3242") and the forum-id exclusion. The description's 'Requires an id' and 'numeric id' add little, and 'numeric' slightly understates the string form the schema permits. 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?

States a specific verb and resource: fetch the FULL text of one indexed Canton-ecosystem documentation page by numeric id. It explicitly scopes the content domain (Canton/Daml/Splice and partner docs), which lets an agent separate it from get_discussion, get_api_reference, and the search tools.

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?

Gives an explicit ordering rule: use AFTER search or semantic_search returns a doc id. It also states the negative case ('Not a discovery tool; use search/semantic_search first'), and the schema reinforces routing by noting forum topic ids belong to get_discussion.

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