Skip to main content
Glama
Podcast MCP
by calebn

document_command_schema_tool

Lists document command types and returns the payload JSON schema for a selected type. Use it to build valid command payloads and identify submittable types or the named tool to use instead.

Instructions

List the document command types, or return one type's payload JSON schema (read only).

With no command_type the result lists every type with submittable (false when submit_document_command_tool refuses it, with the refusal naming the named tool to use), the least guest_role and any host_only_reason. With a type it adds the payload_schema to build the payload from. Time fields follow the command's own payload: read each field's description before you send it. A baseline field (SetEnvelope.expected_points, SetClipFade.expected, TrimClipEdge.expected_token) says there how to read it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "document_command_schema_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
command_typeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the behaviour burden and does so well: it declares read-only, explains the submittable/refusal gating that redirects to another tool, exposes permission context via guest_role and host_only_reason, and warns that time fields must be read from each field's description. It stops short of describing error behaviour or whether the listing is stable across calls.

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?

Front-loaded summary sentence followed by the two modes and then the caveats, so the agent gets the essential contract first. The parenthetical enumerating example baseline fields is dense but earns its place by naming the exact fields that require careful reading.

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?

The tool is simple (one optional parameter) and has an output schema, yet the description still covers the non-obvious parts: why a type may be unsubmittable, what the permission fields mean, and how baseline time fields must be interpreted. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 0% and the single parameter has no documentation, so the description must compensate — and it does, spelling out the null/omitted case versus the with-type case and what each adds to the response. Valid type values are only discoverable indirectly through the no-argument listing, which is a minor remaining gap.

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 opening line states a specific verb and resource plus both operating modes: 'List the document command types, or return one type's payload JSON schema (read only).' It also implicitly separates itself from submit_document_command_tool by explaining that the listing flags types that tool refuses and names the alternative, so an agent can distinguish the schema-lookup tool from the execution tool.

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

Usage Guidelines4/5

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

The description explicitly conditions behaviour on the argument: with no command_type you get the full list; with a type you get payload_schema 'to build the payload from', which tells the agent to call this before submitting a command. What it lacks is an explicit prerequisite statement (e.g. always call this before submit_document_command_tool) or a note about caching/re-calling.

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

Deploy Server

Other Tools