Skip to main content
Glama

say

Continue an active meeting by sending a message, including verdicts on prototypes and a final Prototypes block with the board URL, live prototypes, and those destroyed.

Instructions

Continue a conversation in an active meeting. In a prototype meeting you assess the agent's prototypes: give Verdict on Pn: APPROVE|REVISE|REJECT — reason on its own line, grounded in the artifact and its demo; the reply ends with a Prototypes block (the board URL, live prototypes and those destroyed this call).

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": {
      "meeting_id": "<meeting_id>",
      "message": "<message>"
    },
    "name": "say"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesYour message to the agent.
meeting_idYesThe meeting ID from start_meeting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the write/non-idempotent nature is covered. The description adds genuine value beyond that: it discloses that the reply ends with a Prototypes block containing the board URL and which prototypes are live versus destroyed this call, and it prescribes the exact verdict token set (APPROVE|REVISE|REJECT) required for acceptance.

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

Conciseness4/5

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

Everything is front-loaded: the general purpose comes first, then the prototype-specific protocol. The second sentence is dense but each clause carries required calling instructions; nothing is filler, though the verdict-format clause is packed tightly enough to be easy to misread.

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?

With no output schema, the description carries the burden of describing returns, and it does so for the prototype case (Prototypes block with board URL and destroyed-prototype list). It is thinner about what a normal conversational reply returns, but for a 2-parameter messaging tool the guidance is largely sufficient.

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?

Schema coverage is 100%, so both parameters are already documented and the baseline would be 3. The description still adds meaning beyond the schema by constraining what `message` must contain in a prototype meeting — a `Verdict on Pn:` line with a fixed vocabulary and a grounding requirement — which the schema's 'Your message to the agent' does not convey.

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 opens with a specific verb and resource: 'Continue a conversation in an active meeting,' which tells an agent this sends a message into a running meeting rather than starting or ending one. It doesn't name a sibling such as say_local, so the distinction between meeting types is only implied by the word 'active.'

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?

It gives a clear context for use (an active meeting) plus a conditional branch: in a prototype meeting you must emit a Verdict line in a specific format. There are no explicit when-not rules and no named alternatives, so the agent must infer that non-prototype meetings need no verdict.

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