Skip to main content
Glama
Sign In
opentakeoff-mcp

opentakeoff-mcp

by Kentucky-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

assistant_say

Displays your Markdown reply in the OpenTakeoff Assistant window so the person reading it sees the answer, then prompts you to resume listening for the next message.

Instructions

Show your reply in the OpenTakeoff Assistant window (Markdown). Use it for every answer to a message that came through assistant_listen — the person is reading the window, not this chat. Then call assistant_listen again.

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": {
      "text": "<text>"
    },
    "name": "assistant_say"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesYour reply, Markdown

Output Schema

NameRequiredDescriptionDefault
delivered_toYesOpen windows that received the reply (0 = the person closed the window; it shows when they reopen)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.31

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the non-obvious behavior: the text is rendered for a human in a separate window rather than returned inline, which explains why calling it is mandatory. It does not cover failure modes, size limits, or whether the call blocks waiting for a reply, so the loop semantics are only partly spelled out.

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 sentences, front-loaded with the action, then the obligation, then the follow-up. Nothing is padded and every clause changes how the agent behaves.

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?

The tool is simple, the single parameter is fully documented, and an output schema exists so return values need no explanation. What remains — when to call it and what to do afterwards — is fully covered.

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?

There is a single parameter at 100% schema description coverage, so the schema already documents 'text' and its Markdown format. The description adds only a mild restatement ('your reply'), and offers no constraint details such as length or escaping.

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 states a specific verb and target — 'Show your reply in the OpenTakeoff Assistant window' — and names the transport (Markdown). It is unambiguously distinct from the sibling assistant_listen, which reads messages rather than displaying them.

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?

It gives an explicit trigger ('every answer to a message that came through assistant_listen'), an explicit reason (the person reads the window, not this chat), and an explicit next step ('then call assistant_listen again'). That is when-to-use plus the follow-up protocol, which is what an agent needs here.

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