Aisma

Start an edit (spends credits)

start_edit

Destructive

Starts the edit for a quote and reserves its credits from your Aisma balance. Confirm the price with the user first. Then poll get_job; the finished video lands privately in your Aisma Library.

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": {
      "quoteId": "<quoteId>"
    },
    "name": "start_edit"
  }
}

Input Schema

Name	Required	Description	Default
`quoteId`	Yes

Output Schema

Name	Required	Description	Default
`jobId`	Yes
`status`	Yes
`credits`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds genuinely new behavioral context: credits are reserved from the balance, the user should confirm price first, and the output lands privately in the library. It omits retry/double-charge risk, which matters for a non-idempotent spend.

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?

Three short sentences, front-loaded with the action and cost implication, then the confirmation gate, then the polling workflow. Nothing is redundant.

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 an output schema present, return values need no explanation, and the description covers cost, confirmation, and the get_job polling loop. Missing only failure modes such as insufficient balance or quote expiry.

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?

Only one parameter and the schema has 0% description coverage, so the description must carry the burden. It implies quoteId comes from a quote ('for a quote') but never states the format, origin tool, or validity constraints (e.g. quote expiry). Useful hint, incomplete compensation.

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?

States a specific verb and resource ('Starts the edit for a quote') plus the side effect that matters most ('reserves its credits'). An agent can distinguish it from quote_edit and get_job, though it never names quote_edit as the source of the quoteId, so sibling differentiation is implied rather than explicit.

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?

'Confirm the price with the user first. Then poll get_job' gives an explicit pre-condition and an explicit follow-up tool, which is exactly the sequencing an agent needs. It stops short of stating when-not-to-use (e.g. quote not yet obtained or expired).

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.