ismail: agent DAW (MCP server)

Overview Schema Source Related Servers Discussions Admin

Stage Ask

stage_ask

Ask a yes/no question aloud in VR and wait for a thumbs-up or thumbs-down answer, enabling hands-free sign-off during headset workflows.

Instructions

Ask a yes/no question out loud and wait for a RIGHT thumbs up (yes) or down (no) held 400 ms (page command: ask). Waits until answered or seconds pass; other commands go on meanwhile. Use it for every sign-off in the headset (a reload, a re-export). Only answerable in VR (the thumbs are hand gestures). A second ask while one is open does not raise: the page replies {error: 'already asking: ...'} (the op should turn that into OpError). Page replies {question, answer: yes | no | 'no answer', seconds}. Emits: answer, voice_spoken, voice_error. While it waits, the question shows over the person's right hand (the hand that answers) with what up and down mean, under sender= (your name as they know it). Refused when a standing grant already answers it (~/.ismail/standing_grants.json): act on the grant and say what you did; override_grant='' asks anyway and logs the reason.

Input Schema

Name	Required	Description	Default
`text`	Yes
`scene`	Yes
`sender`	No
`seconds`	No
`override_grant`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Oct 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With zero annotations, the description carries the full burden and executes it perfectly. It details mechanism (400ms hold), failure modes (already asking error), UI behavior (question over hand), and complex business logic (handling standing grants and override).

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

Conciseness3/5

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

The definition is extremely dense and verbose, making it difficult to parse quickly. While every sentence adds value, the lack of structuring or breaking up the paragraphs detract from its conciseness.

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?

Given the complexity of hand gestures, state management, and security grants, the description is exhaustively complete, leaving almost no ambiguity for an agent deciding whether or how to invoke it.

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

Parameters5/5

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

Since schema coverage is 0%, the description must define everything. It provides semantic meaning for every parameter, including the specific logic behind `override_grant` and the default behavior of `seconds`.

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 purpose is perfectly clear: to ask a yes/no question out loud in VR and wait for a specific gesture (thumbs up/down). It is distinct from other voice or scene-manipulation tools.

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

Usage Guidelines5/5

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

The description specifies the operational context ('Use it for every sign-off in the headset') and the required environment (VR only), effectively defining when and where this tool must be used.

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

Deploy Server