Skip to main content
Glama
Sign In
noisy-coding

noisy-coding

Official
by noisy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

announce

Speak a quick progress update without waiting for it to finish, letting you keep working while the message plays in the background. Announce completed steps and move on immediately.

Instructions

Speak a quick spoken update WITHOUT waiting for it to finish.

Fire-and-forget: use this to tell the user what you just did and keep working ("done with X, moving on") — it returns immediately and plays in the background, queued behind any current speech. Use speak instead when you are asking a question or otherwise waiting for the user's reply. Like speak, it carries only text — voice/speed/language live in the daemon.

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": "announce"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.13.4

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries full behavioral burden. It discloses that the tool returns immediately, plays in the background, queues behind current speech, and carries only text. This is thorough and gives the agent a clear model of runtime behavior.

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?

The description is compact and well-structured, front-loading the core behavior in the first sentence and building on it with usage guidance. Every sentence adds value, with no redundancy or fluff.

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?

For a simple one-parameter tool with an output schema present, this description covers purpose, usage, behavior, and parameter meaning fully. It is complete and leaves no significant gaps for an agent to operate correctly.

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?

The single 'text' parameter has zero schema documentation, but the description compensates by stating the tool 'carries only text' and that voice/speed/language live in the daemon, clarifying that the text parameter is the complete content with no hidden options.

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 opens with a specific verb and resource: 'Speak a quick spoken update WITHOUT waiting for it to finish.' It directly distinguishes the tool from its sibling 'speak' by emphasizing the fire-and-forget behavior, making the purpose unmistakable.

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?

Explicit guidance is provided: use this for quick updates while continuing work, and 'Use `speak` instead when you are asking a question or otherwise waiting for the user's reply.' This clearly states when to use this tool versus an alternative.

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