Skip to main content
Glama
Sign In
mcp-for-cascadeur

mcp-for-cascadeur

by Rickcy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

action_run

Destructive

Dispatch a listed native action on the expected Cascadeur scene, then report dispatch status and inspect completion.

Instructions

Dispatch an exact listed native action on the expected scene; report dispatch, then inspect completion.

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": {
      "action_id": "<action_id>",
      "expected_scene": "<expected_scene>"
    },
    "name": "action_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
action_idYes
expected_sceneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already flag this as mutating and destructive (destructiveHint=true), so the description's key burden is to say what it destroys, whether it is reversible, and what permissions it needs. It adds one genuinely useful behavioral fact — that dispatch reports separately from completion, implying an asynchronous two-phase outcome — but says nothing about irreversible effects or failure recovery despite being destructive.

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?

A single front-loaded sentence with no filler; the two clauses map cleanly to dispatch and verification. It is terse to the point of being cryptic about the completion check, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, no-output-schema tool with 0% parameter coverage, the agent needs to know the source of action_id, the form of expected_scene, and how to confirm completion. The description gestures at the last point but leaves the first two unresolved.

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

Parameters2/5

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

Schema coverage is 0%, so all semantic load falls on the description. It conveys that action_id must match an enumerated action and that expected_scene acts as a guard, but never defines expected_scene's format (name vs. id vs. path) or where either value should be obtained, leaving both required parameters under-specified.

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 ('Dispatch an exact listed native action') plus the scoping requirement ('on the expected scene'). It is distinguishable from siblings like actions_list or scene_activate, though 'native action' is a term the agent must infer.

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?

Usage is only implied: 'listed' hints that action_id must come from actions_list and 'expected' hints at a precondition check, but the description never names the sibling to call first nor states when not to use this tool.

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

Deploy Server

Other Tools