CueFrame

Describe Composition Operations

describe_composition_ops

Read-onlyIdempotent

Discover the exact CompositionOp vocabulary accepted by apply_composition. Omit type for a compact list of operation names and descriptions; pass type for only that operation's JSON Schema. Read this before authoring edits or captions.

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": "describe_composition_ops"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No	Exact CompositionOp type, such as captions.fromComposition. Omit for the operation list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 28, 2026
- addedInput schema / $defs
```
Added value: +{
+  "__schema0": {
+    "type": "string"
+  }
+}
```
- addedInput schema / properties / type / $ref
```
Added value: +"#/$defs/__schema0"
```
- removedInput schema / properties / type / type
```
Removed value: -"string"
```
First observedOct 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description earns credit by disclosing that the return payload differs by mode — a name/description list when type is omitted versus a JSON Schema for one op when supplied — which the annotations cannot convey.

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 clauses, zero filler: purpose first, mode behavior second, call-site guidance last. Nothing could be removed without losing information.

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

Completeness5/5

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

With one optional parameter, full schema coverage, and no output schema, the description covers everything an agent needs: what the tool returns in each mode and when to invoke it. No output schema means return-shape disclosure falls to the description, and it delivers exactly that.

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?

Schema coverage is 100% and the parameter's description already says 'Omit for the operation list', so the description largely restates schema content. It clarifies the consequence of each mode, which is mildly additive, but under the high-coverage rule the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Discover the exact CompositionOp vocabulary') and ties it directly to the sibling that consumes it (apply_composition). An agent can immediately separate this discovery tool from apply_composition or validate_composition without inspecting schemas.

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?

Gives an explicit trigger ('Read this before authoring edits or captions') and explains mode selection: omit type for the compact list, pass type for a single schema. It stops short of stating when not to call it or naming alternatives beyond apply_composition, so it is strong but not exhaustive.

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

All CueFrame 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.