Get one Mographr tool's full schema: customizable fields (with max lengths and examples), design-system variants (use the variant id when rendering), color schemes, output size and an example render call.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Tool slug from list_motion_tools, e.g. "lower-thirds" |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds meaningful behavioral context beyond the annotations by detailing what the schema includes: customizable fields with max lengths/examples, design-system variants, color schemes, output size, and an example render call. Since readOnlyHint already indicates a safe read operation, the description enriches the return content without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that conveys the core purpose and then lists the contents in an easy-to-parse colon-separated list. Every word adds value; there is no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with one parameter and no output schema, the description is quite complete: it enumerates the key content of the returned schema. It does not mention error handling or prerequisites, but these are not critical for a tool of this simplicity. The parameter schema covers the source of the slug, filling a potential gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides full coverage for the lone parameter slug with a clear description and example. The description does not add further parameter syntax but reinforces that the parameter identifies a single tool. With 100% schema coverage, baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states "Get one Mographr tool's full schema" which specifies the action (get) and the resource (one tool's schema). It differentiates from siblings by focusing on schema retrieval rather than listing tools or rendering, and enumerates specific contents (fields, variants, colors, output size, example call).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when you need detailed schema information for a specific tool, but does not explicitly state when to use it over alternatives like list_motion_tools or render_motion_tool. The schema parameter mentions that the slug comes from list_motion_tools, but this is in the schema, not the description. No exclusions or alternative guidance are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, distinct role: listing available tools, fetching a tool's schema, initiating a render, and polling render status. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern: list_motion_tools, get_motion_tool, render_motion_tool, get_motion_render. The verbs clearly indicate the action, and the nouns are consistent.
Four tools is well-suited for this server's scope—covering discovery, schema inspection, rendering, and polling. No tool feels redundant or missing.
The tool set covers the full workflow: list available templates, get detailed customization options, render a video, and retrieve the result. There are no obvious gaps for the stated purpose.