Skip to main content
Glama
Sign In
Cavalry MCP Bridge

Cavalry MCP Bridge

by matthewobanla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cavalry_get_frame

Retrieve the current playhead frame number from an active Cavalry composition to track animation timing or synchronize actions.

Instructions

Returns the current playhead frame number in the active composition.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description must disclose all behavioral traits. It indicates a read operation (no side effects) but fails to mention prerequisites (active composition required) or error behavior if none exists. Adequate for simple getter but not comprehensive.

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?

Single sentence that is front-loaded with the verb and resource. No fluff. Every word earns its place.

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 zero parameters and no output schema, the description mostly suffices but could clarify the return type (integer vs float). The mention of 'active composition' hints at context, but no mention of error if no composition open. Nearly complete for a simple getter.

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

Parameters4/5

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

There are zero parameters, so the description needs no extra parameter info. Schema coverage is 100% trivially. The description adds no param meaning because none exist. Baseline 4 for 0 parameters 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?

The description clearly states the verb 'Returns' and resource 'current playhead frame number in the active composition,' which precisely distinguishes it from sibling tools like cavalry_set_frame and cavalry_playback_control. No ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like cavalry_set_frame or cavalry_playback_control. No when-not-to-use or context for optimal invocation.

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