Skip to main content
Glama

bridge_log

Logs bridge activity through the v2 service by recording what occurred and an optional project for shared task-board tracking.

Instructions

Execute bridge log 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": {
      "what": "<what>"
    },
    "name": "bridge_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYes
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?

With no annotations, the description carries the full disclosure burden, and it discloses nothing: it is unclear whether this writes a log entry, reads existing logs, or triggers a background process, nor what permissions are needed or whether effects are reversible. "Execute" is the only hint and is ambiguous between read and write.

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 words on a restatement plus an uninformative version reference, leaving the definition under-specified rather than concise. There is no front-loaded statement of purpose an agent could act on.

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?

Given zero annotation coverage, zero schema description coverage, no output schema, and a required parameter named only "what," this definition is far too thin for an agent to select or invoke the tool correctly.

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%, so the description must compensate for both parameters. It never mentions the required "what" parameter or the optional "project" parameter, leaving the agent with no idea what values belong in either.

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 log" largely restates the tool name with a generic verb and never says what a bridge log is or what executing one produces. The only added information is "through the v2 service," which does not distinguish it from any of the many bridge_* siblings.

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 prerequisites, and no mention of alternatives such as bridge_activity or bridge_export, which an agent could plausibly confuse with logging. Nothing tells the agent under what condition this tool is the right choice.

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