Skip to main content
Glama

Dynamic Document API

by com.dynamicdocumentapi
OverviewDiscussionsAdmin

List Dynamic Document API templates

list_templates
Read-onlyIdempotent

List the published templates of the connected workspace: id, name, type and live version. Use it to find the template_id for a document the user describes; skip it when you already have the id. PDF templates (pdf_code, pdf_markdown) go to render_pdf_from_template, image templates (image_canvas) to render_image_from_template; call get_template_schema next for the data a template expects. Returns 50 templates per page unless limit says otherwise; pass next_cursor as cursor while has_more. Not billed. Limited to 60 tool calls a minute per connection, shared by all tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOnly return templates of this type, e.g. `image_canvas` for image templates.
limitNoPage size, 1-100 (default 50).
queryNoPart of a template name, case-insensitive.
cursorNo`next_cursor` of the previous page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
has_moreYesMore templates match: call again with `cursor: next_cursor`.
templatesYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor from a previous call."New value: +"`next_cursor` of the previous page."
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search over template names."New value: +"Part of a template name, case-insensitive."
    • changedInput schema / properties / type / description
      Previous value: -"Only return templates of this type."New value: +"Only return templates of this type, e.g. `image_canvas` for image templates."
    • addedOutput schema / properties / has_more / description
      Added value: +"More templates match: call again with `cursor: next_cursor`."
    • addedOutput schema / properties / templates / items / properties / id / description
      Added value: +"Template id (`tpl_…`), the `template_id` of the render tools."
    • addedOutput schema / properties / templates / items / properties / live_version / description
      Added value: +"The version renders use by default."
    • addedOutput schema / properties / templates / items / properties / type / description
      Added value: +"`pdf_code`, `pdf_markdown`, `image_canvas`, `docx` or `pdf_form`."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (which only declare it as a safe, idempotent read), the description adds pagination behavior (50 per page, next_cursor/has_more contract), the billing status ('Not billed'), and a concrete rate limit shared across all tools. These are operational facts an agent cannot derive from the schema or 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?

Information-dense and front-loaded: purpose, usage, routing, pagination, then cost/limits. Every clause carries distinct operational information with no filler.

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?

An output schema exists so return values need no explanation; the description covers everything else an agent needs — discovery role, sibling routing, pagination loop, and throttling — for a 4-parameter read tool with an enum filter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and self-documenting, but the description still adds value by restating the 50-item default and explaining the cursor contract ('pass next_cursor as cursor while has_more'), which links the request parameter to the response field.

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 ('List the published templates of the connected workspace') and enumerates the returned fields (id, name, type, live version). This clearly separates it from the render_* and get_template_schema siblings.

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 explicit when-to-use ('find the template_id for a document the user describes'), explicit when-not ('skip it when you already have the id'), and routes by template type to render_pdf_from_template or render_image_from_template, plus names get_template_schema as the logical next call.

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

All Dynamic Document API 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