Skip to main content
Glama
newsbubbles

ismail: agent DAW (MCP server)

Stage Take View

stage_take_view

Display a take in 4D by visualizing head and wrist paths plus 2–24 ghost poses, colored blue to orange, in strip or place layout to review motion.

Instructions

Show a take in 4D: the paths of the head and both wrists and n ghost poses (2..24) coloured blue to orange (page command: take_view). layout: strip (a filmstrip in front of the person, 40 cm apart) | place (where it happened). BUG today: the page reads the take id from the command's id, but server.py drops a sent id and puts its own command number there (only marker gets a rename to marker_id), so from the live link this looks for take "" and fails; it works only from the page's own review menu. The op should send the take under its own field and the page read it. Errors: no take, no frames. Page replies {id, poses, seconds, frames}. Emits: take_view.

Input Schema

NameRequiredDescriptionDefault
nNo
takeYes
sceneYes
layoutNostrip

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose important behavior: the visual output, n range, layout modes, emitted event, error cases, and a critical live-link bug. It is unusually transparent, though the bug narrative mixes implementation advice with caller-facing behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a long, run-on mix of purpose, layout options, a bug report, server.py internals, error cases, and reply shape. The valuable information is present but poorly front-loaded and not cleanly separated.

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

Completeness3/5

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

It covers the visual purpose, some parameter semantics, errors, emitted event, and reply shape. But for a tool with four parameters, zero schema coverage, and no annotations, it leaves the required `scene` parameter unexplained and offers no sibling-tool routing.

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%, so the description must compensate. It explains `n` (ghost poses 2..24) and `layout` (strip|place), and indirectly references the take id, but it never defines the required `scene` parameter and adds confusion around how `take` is sent.

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 states a specific verb and resource: 'Show a take in 4D' with head/wrist paths and ghost poses. It is fairly clear what the tool does, though it does not explicitly differentiate itself from siblings such as stage_takes or stage_take_view_clear.

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?

It implies usage through 'page command: take_view' and a caveat that the tool works only from the page's review menu. However, it never states when to use this tool instead of alternatives like stage_take_replay or stage_take_view_clear.

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