Skip to main content
Glama

say_local

Continue an active local CLI meeting by sending a message to the agent and submitting a prototype verdict (APPROVE, REVISE, or REJECT) with a clear reason.

Instructions

Continue a conversation in an active LOCAL meeting (CLI-based). In a prototype meeting give Verdict on Pn: APPROVE|REVISE|REJECT — reason for the agent's prototypes; the reply ends with a Prototypes block.

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_local"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesYour message to the agent.
meeting_idYesThe local meeting ID from start_local_meeting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare write, non-idempotent, open-world, non-destructive. The description adds genuinely new behavior: the reply ends with a Prototypes block and prototype verdicts require an exact `Verdict on Pn: APPROVE|REVISE|REJECT — reason` syntax. It does not say whether the call blocks awaiting the agent, what happens if the meeting is ended, or what a failed send looks like — important for a non-idempotent write.

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?

Two sentences, front-loaded with the action and scope, then the special-case instruction. Dense but every clause carries information; the second sentence is compact to the point of being slightly cryptic on first read.

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?

With 2 well-documented params and no output schema, the essentials are covered, and the partial mention of the Prototypes block hints at return shape. The gap is interaction semantics: whether the call waits for the agent's response and how failures surface is unaddressed for a non-idempotent write tool.

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 3 is the baseline. The description goes beyond that by constraining the *content* of `message` in prototype meetings to a specific verdict format, which the schema 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?

States a concrete verb and resource — 'Continue a conversation in an active LOCAL meeting (CLI-based)' — which pins down both the action and the environment. The capitalized LOCAL implicitly separates it from the sibling 'say', though it never names that sibling outright.

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?

The description tells the agent this applies to an *active* local meeting and adds a conditional case for prototype meetings. It never states when to prefer it over 'say' or 'await_subtasks', so the agent must infer the local-vs-other routing from the capitalized LOCAL alone.

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