Skip to main content
Glama
Sign In
Chorono

Chorono

by codie1982
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_parameter

Creates a named runtime scene parameter—number, boolean, color, or string—so triggers, bindings, wires, and state-machine guards can read and write its value.

Instructions

Add a scene parameter — a named runtime value (number/boolean/color/string) that triggers, bindings, wires, and state-machine guards can read and write.

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": {
      "id": "<id>"
    },
    "name": "add_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique parameter id e.g. "score"
maxNoMax (number params)
minNoMin (number params) — drives slider range
nameNoDisplay name
typeNoParameter type (default number)
requestIdNo
sessionIdNo
defaultValueNoInitial value (number/bool/hex color/string)
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 agent knows this is a local write. The description adds that the created value is shared runtime state consumed by triggers/bindings/wires/guards, which is useful context, but says nothing about duplicate-id behavior, whether it fails or overwrites, or how expectedRevision/sessionId affect the write.

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?

A single sentence with zero filler, front-loading the action and the resource, then the clarifying definition of what a parameter is. Nothing could be cut without losing information.

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?

Given nine parameters, no output schema, and a moderately documented schema, the description covers the conceptual role of the artifact well, which is the main thing an agent needs. It falls short on lifecycle details (uniqueness of id, revision/session semantics) that matter for a mutating create operation in a scene graph.

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?

With 67% schema coverage the schema already explains min/max slider behavior and defaultValue formats, so the description need only complement it. It instead restates the type list while omitting the schema's fifth enum value ("image"), and adds no meaning for expectedRevision, requestId, or sessionId.

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?

Uses a specific verb plus resource ("Add a scene parameter") and immediately defines the artifact: a named runtime value readable and writable by triggers, bindings, wires, and state-machine guards. That definition lets an agent distinguish it from siblings like add_parameter_wire or add_binding, though it never names those siblings explicitly.

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: the tool is for creating a value that other constructs consume, which hints at when to reach for it, but there is no explicit when-to-use, no ordering guidance (e.g. that it should precede add_parameter_wire or add_trigger), and no exclusions relative to the many sibling mutation tools.

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