Skip to main content
Glama

Get a draft

get_draft
Read-onlyIdempotent

Read a draft: its scenes (narration, visual prompt, length), whether the narration is long enough for the target duration, and the exact render price against the current balance. Free, read-only. Requires the "video:read" scope.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "draftId": "<draftId>"
    },
    "name": "get_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond those hints: the call is free (no credit consumption), it requires the 'video:read' scope, and it performs a duration-adequacy evaluation rather than just returning raw data.

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?

One sentence front-loads the core action and its return payload, followed by two terse clauses for cost and authorization. Nothing is redundant and nothing could be cut without losing information.

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 no output schema, the description does the work of describing the return shape (scenes, duration check, price vs balance) and discloses the scope requirement. The only real gap is that draftId is never explained, which is minor for a single-parameter read.

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?

There is one parameter with 0% schema description coverage, so the description carries the burden of explaining draftId but never mentions it. The parameter is self-evidently the draft identifier, which keeps this at an acceptable baseline, but no format, source, or example is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Read a draft') and then enumerates exactly what the read returns: scenes with narration/visual prompt/length, a duration-adequacy check, and render price against balance. That is far more informative than the title, though it never distinguishes itself from the sibling get_video or render_draft, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the mention of render price against balance suggests calling this before render_draft, and 'Free, read-only' signals it is a safe pre-flight check. However, there is no explicit when-to-use/when-not-to-use statement and no named alternative, so the agent has to construct the workflow itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources