Skip to main content
Glama
Sign In
Chorono

Chorono

by codie1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

control_runtime

Set live runtime parameters and dispatch state-machine events to drive animation transitions and blends during paused test ticks, and stop test ticks when test mode is disabled.

Instructions

Set live runtime parameters and dispatch a state-machine event. Events enable runtime test ticks so transitions/blends work while paused; testMode:false stops test ticks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "control_runtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventNo
testModeNo
machineIdNo
requestIdNo
sessionIdNo
parametersNo
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=false, so the mutation/non-open-world profile is known. The description adds genuinely useful behavior about test ticks and that testMode:false stops them, but says nothing about concurrency (expectedRevision), idempotency (requestId), or what happens to unspecified parameters.

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?

Two tight sentences with the core action front-loaded and the testMode caveat following. Dense domain jargon (runtime test ticks, blends) but no wasted wording.

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?

A mutating, 7-parameter tool with a nested object, zero schema descriptions, and no output schema needs substantially more than two sentences. An agent cannot know how to populate machineId/sessionId/requestId or how expectedRevision affects the call.

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 description coverage is 0% across 7 parameters, including a nested 'parameters' object, so the description must compensate and largely does not. It clarifies only 'event' and 'testMode'; machineId, requestId, sessionId, parameters, and expectedRevision are entirely undefined anywhere.

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 names a specific verb+resource pair: setting live runtime parameters and dispatching a state-machine event. That clearly separates it from read-side siblings like get_runtime and evaluate_frame, though it never explicitly names those alternatives.

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 through the test-tick explanation: use it when you need transitions/blends to progress while playback is paused. There is no explicit statement of when to prefer control_playback, get_runtime, or evaluate_frame, and no prerequisites or exclusions.

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