Skip to main content
Glama

Todrawn Scribe limits

scribe_limits
Read-onlyIdempotent

Check accepted input types and Free/Premium plan limits before building a handwriting-style video project.

Instructions

Lists what Todrawn Scribe accepts and what the Free and Premium plans allow, before building a video.

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": "scribe_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so the safety profile is covered. The description adds that the returned content is capability and plan-tier information (what is accepted, what Free vs Premium allows), but does not say anything about the shape or granularity of that listing. Reasonable value on top of annotations, not rich.

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?

A single sentence with the verb and content front-loaded and the usage cue at the end. Every clause carries information: accepted inputs, plan tiers, and timing relative to video creation.

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?

For a zero-parameter, read-only informational tool with annotations covering safety, the description conveys enough to call it confidently. The only minor gap is that, with no output schema present, it does not describe how the limits are laid out in the response.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. It offers no misleading parameter-like language.

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 gives a concrete verb ('Lists') and a specific resource: what Todrawn Scribe accepts plus Free/Premium plan allowances. That is far more precise than a tautological restatement of the name, though it does not explicitly contrast itself with siblings such as scribe_create_video.

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 only implied by the trailing phrase 'before building a video', which suggests calling it as a pre-flight check. No alternative is named and there are no explicit when-not conditions, so the agent must infer the timing.

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