Skip to main content
Glama

bridge_activity

Retrieve recent cross-agent activity from the v2 service, filtered by project or timestamp, to track tasks, questions, reviews, and replies exchanged through the shared task board.

Instructions

Execute bridge activity through the v2 service.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bridge_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNo
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether "execute" is a read or a mutation, not whether it requires authentication, and not what side effects or failures to expect. The phrase "execute ... activity" actively obscures the operation type.

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 that brevity comes from under-specification rather than economy; it front-loads nothing useful because there is nothing to front-load. Not bloated, but it earns almost none of its space.

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?

With no annotations, no output schema, zero parameter documentation, and two unexplained parameters, the definition is far too thin for an agent to invoke this tool correctly. Nothing in the description compensates for the missing structured metadata.

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% for two parameters (since, project), and the description says nothing about either. An agent cannot tell what format "since" expects (timestamp, ID, date string) or whether "project" is a name, key, or path, nor what the empty required list implies.

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 activity" essentially restates the tool name (bridge_activity) rather than explaining what operation is performed; the only added information is that it goes through "the v2 service." It gives no basis for distinguishing this from any of the 22 sibling bridge_* tools.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no preconditions, no exclusions, and no named alternative among the many bridge_* siblings. An agent has no signal for choosing this tool over bridge_log, bridge_status, or bridge_show.

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