Skip to main content
Glama

bridge_wake

Sends a wake signal to a specified agent through the v2 service, optionally scoped to a project, so it can resume shared task-board work.

Instructions

Execute bridge wake through the v2 service.

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": {
      "agent": "<agent>"
    },
    "name": "bridge_wake"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden and discloses nothing: not whether waking mutates state, what side effects occur, whether the agent must be idle, or what happens if it is already awake. 'Execute' hints at an action but gives no behavioral detail.

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

Conciseness2/5

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

The single sentence is short but wastes its only clause on the tautological "bridge wake" and an uninformative service-version note. Brevity here reflects under-specification rather than efficient communication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an action tool with a required parameter, no annotations, and no output schema, the description provides nothing an agent needs in order to invoke it correctly. It is materially inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description never mentions the required 'agent' parameter or the optional 'project' parameter, nor their formats or relationships. The two parameters are completely undocumented in both schema and prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Execute bridge wake" largely restates the tool name rather than defining the operation; nothing explains what a 'wake' does or what object it targets. The only added information is a reference to a 'v2 service', which does not help an agent distinguish this from siblings like bridge_agents or bridge_claim.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus any of the many sibling bridge_* tools, nor any stated preconditions or exclusions. An agent must guess the trigger condition entirely.

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