Aisma

Price an edit

quote_edit

Read-onlyIdempotent

Prices an edit of a ready source video with an instruction (the brief) and optional reference photos, at 720p (default) or 1080p. Nothing is charged. The price in credits holds for 15 minutes. If it answers pending, call again after retryAfterMs. The original framing and audio are kept.

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": {
      "sourceId": "<sourceId>",
      "brief": "<brief>"
    },
    "name": "quote_edit"
  }
}

Input Schema

Name	Required	Description	Default
`brief`	Yes	What to change, in your own words. Refer to photos by their label: "photo 1".
`photos`	No
`quality`	No		720p
`sourceId`	Yes

Output Schema

Name	Required	Description	Default
`id`	No
`credits`	No
`pending`	No
`expiresAt`	No
`retryAfterMs`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing that no credits are charged, that the quote expires after 15 minutes, the asynchronous 'pending' + retryAfterMs pattern, and that original framing and audio are preserved. These are exactly the behavioral facts an agent needs to call and re-call this tool safely.

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?

Four compact sentences, front-loaded with what the tool does and immediately followed by the no-charge and expiry constraints. No filler and no repetition of annotation or schema content.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers the one non-obvious return state (pending + retryAfterMs) plus price validity. Minor gaps remain around photo limits and what 'ready source' requires, but nothing critical is missing for a correct call.

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 only 25% (only brief is documented), so the description has to compensate and largely does: it explains brief as 'the instruction', photos as optional reference material, and quality as 720p default / 1080p. sourceId is only obliquely covered by 'ready source video', and the 10-photo cap and label referencing are left to the schema.

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 and resource ('Prices an edit of a ready source video') plus the inputs that define it (brief, optional photos, resolution). The pricing framing cleanly separates it from the sibling start_edit, which actually executes the edit, without needing to open 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 Guidelines4/5

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

Gives concrete operating guidance: nothing is charged, the quote is valid for 15 minutes, and a 'pending' response means calling again after retryAfterMs. It stops short of explicitly naming start_edit as the follow-up step or stating prerequisites for a 'ready' source, so the sequencing is implied rather than spelled out.

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

All Aisma tools Inspect

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.