Skip to main content
Glama

nudge_collaboration

Injects an orchestrator message into a collaboration to redirect discussion, ask clarifying questions, or supply context; do not use it to relay prototype feedback while assessment is active.

Instructions

Inject a message from the orchestrator into the collaboration. Use to redirect discussion, ask clarifying questions, or provide additional context. In a prototype session nudges are refused while a prototype is under assessment; never use a nudge to relay the human's feedback on prototypes before the session ends.

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": {
      "collaboration_id": "<collaboration_id>",
      "message": "<message>"
    },
    "name": "nudge_collaboration"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesYour message to inject into the discussion. Will appear as from ORCHESTRATOR.
collaboration_idYesThe collaboration ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (which only mark it as a non-read-only, non-idempotent, non-destructive open-world write), the description discloses that the message surfaces as coming from ORCHESTRATOR and that the call can be refused in a specific session state. It does not say whether delivery is immediate, whether the discussion is interrupted, or whether the nudge is persisted in the transcript, so it stops short of full behavioral disclosure.

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?

Purpose is front-loaded in the first sentence, followed by use cases and then constraints. The two prototype-related sentences overlap somewhat (both concern prototype feedback timing), costing a little economy, but nothing is wasted overall.

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?

For a two-parameter write with full schema coverage, no output schema, and annotations covering the safety profile, the description supplies the missing pieces: purpose, selection guidance, and the refusal condition. Only the post-delivery behavior (effect on the ongoing discussion, transcript visibility) is left unstated.

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?

Schema coverage is 100%, and both parameters already carry descriptions, including the 'appears as from ORCHESTRATOR' detail. The prose adds no format, length, or targeting semantics for collaboration_id or message beyond what the schema states, so the baseline of 3 applies.

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 names a specific verb and resource ('Inject a message ... into the collaboration') and identifies the sender as the orchestrator, which separates it from sibling posting/chat tools. An agent knows exactly what action this performs without opening the schema.

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 three concrete use cases (redirect discussion, ask clarifying questions, provide additional context) and two explicit prohibitions: nudges are refused while a prototype is under assessment, and a nudge must never relay the human's prototype feedback before the session ends. Both when-to-use and when-not-to-use are stated rather than implied.

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