Skip to main content
Glama
Sign In

AskEditor

by com.askeditor
OverviewDiscussionsAdmin

Ask AskEditor's agent

ask_askeditor
Destructive

[write · costs credits] Takes project_id and instruction. Hand an instruction to AskEditor's own agent, which applies its house skills and runs the tools itself (billed as a chat turn plus whatever it makes). Returns its answer, the tools it ran and, when it exported a film, export with its download_url (pass that on; never retype it). Use it for craft work (a hook, a camera, a title card, a caption style); use the direct tools for precise edits.

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": {
      "project_id": "<project_id>",
      "instruction": "<instruction>"
    },
    "name": "ask_askeditor"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerNoThe person's answer to a plan's stop, when the last answer carried stop: { stop_id }. approve true passes it; changes (their words) keeps it closed; inputs are the ones it asked for, exactly as they wrote them.
approveNotrue only after the person said yes to what this turn spends (a template's quote, or a step that answered needs_yes with its price).
project_idYesThe AskEditor project (from list_projects).
instructionYesWhat to do, as you would type it in the chat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which only flag write/openWorld/destructive/non-idempotent) by disclosing the credit cost model ('a chat turn plus whatever it makes') and that the agent spends on its own. It also describes the return payload — answer, tools run, and export with download_url — plus the operational rule to pass the URL on and never retype it.

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-loads the critical signal ('[write · costs credits]') and wastes nothing, but the return-value sentence is compressed into an awkward clause ('when it exported a film, export with its download_url') that costs a re-read.

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?

For a high-complexity, credit-consuming agent-invocation tool with no output schema, the description covers cost, self-directed tool execution, and the shape of results including the download_url handoff. The approval/stop flow lives in the schema, so nothing an agent needs 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.

Parameters3/5

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

Schema coverage is 100%, so project_id, instruction, approve and the nested answer object are already fully documented in the schema. The description only restates 'takes project_id and instruction' and adds no semantics for the approval gate or stop/inputs fields, so baseline 3 applies.

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+resource: it hands an instruction to AskEditor's own agent, which applies house skills and runs tools itself. It also distinguishes itself explicitly from the direct sibling tools (add_keyframe, set_text, export_video, etc.), so an agent can route without opening either schema.

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 an explicit split: 'Use it for craft work (a hook, a camera, a title card, a caption style); use the direct tools for precise edits.' Both the when and the when-not, plus the named alternative category, are present.

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

All AskEditor 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