Skip to main content
Glama

arsaze_call

Destructive

Run any Arsaze tool from the catalogue by name.

tool: exact name from arsaze_tools (e.g. "split_clip_at"). args: that tool's arguments as an object.
confirm: true only for a destructive/credit-spending tool the user explicitly asked for.
response_detail: "summary" (default — ids + what changed) | "ids" (every id, no timeline) | "compact" (the
whole timeline, nulls stripped) | "full". Over-budget results
come back as a workspace file path to ws_grep/ws_read instead of inline.
fields: dotted paths to return only those parts, e.g. ["clips[].id"]. cursor: next page of a long list.
A bad call returns the tool's exact signature — fix the args and call again.

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": {
      "tool": "<tool>"
    },
    "name": "arsaze_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
toolYes
cursorNo
fieldsNo
confirmNo
response_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 openWorldHint=true, so the bar is lower, yet the description still adds substantive behavior: the confirm gate for destructive/credit-spending tools, the fact that over-budget results are returned as a workspace file path for ws_grep/ws_read instead of inline, and that a failed call echoes the tool's exact signature so args can be corrected. The only gap is that it does not state whether calls are transactional or what happens on partial failure across a mutating tool.

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?

The description is dense and front-loaded, with the primary parameter first and secondary output-shaping parameters after; nearly every clause carries new information. Minor deductions for line breaks that split a sentence mid-clause around 'response_detail' and for not visually grouping the three output-shaping parameters (response_detail, fields, cursor) that operate together.

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 an open-world dispatcher with no output schema and zero schema coverage, the definition covers discovery source, argument passing, mutation gating, response shaping, pagination, large-result offloading, and error recovery. What remains unstated is the scope of the catalogue itself and any auth or workspace context requirements, though the former is plausibly covered by the arsaze_tools sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

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

Schema description coverage is 0% across six parameters, so the description carries the full burden and does so for every one: 'tool' with a concrete example, 'args' as the target tool's argument object, 'confirm' with its gating rule, 'response_detail' with all four accepted values and what each returns, 'fields' with dotted-path syntax and an array example, and 'cursor' for pagination. This is exactly the compensation the low coverage requires, including supplying the value set that the schema leaves as an unconstrained string.

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 opens with a specific verb and resource ('Run any Arsaze tool from the catalogue by name') and immediately explains that the target is named via the 'tool' parameter drawn from arsaze_tools, which distinguishes it from the catalogue-listing sibling. It is clear what the tool does, though as a generic dispatcher it never characterizes the domain of tools it can reach.

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?

It routes the agent to arsaze_tools for discovery and gives a real usage rule for 'confirm' ('true only for a destructive/credit-spending tool the user explicitly asked for'), which is genuine when-to guidance. However, it never says when to prefer the dedicated siblings (arsaze_show_credits, arsaze_estimate_generation_cost, arsaze_show_generated_results) over dispatching through arsaze_call, leaving a meaningful routing decision unaddressed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.