Skip to main content
Glama

bridge_inbox

Retrieves messages and tasks from the shared inbox with limit and cursor pagination, enabling Claude Code and Codex to sync work through a local SQLite task board.

Instructions

Execute bridge inbox 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_inbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo

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 behavioral burden, yet "Execute" is ambiguous about whether this reads or writes and whether side effects occur. Nothing is said about pagination behavior, permissions, or what the two parameters control, despite both being pagination-style arguments.

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?

It is a single short sentence with no filler, but brevity here comes from under-specification rather than economy — there is no front-loaded statement of purpose or scope to anchor the reader.

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, and two undocumented parameters, the definition provides none of the context needed to invoke the tool correctly. An agent cannot determine the operation's effect, return shape, or how to page results.

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% and the description mentions neither "limit" nor "cursor", so an agent gets no meaning beyond the bare property names and types. With two undocumented parameters explicitly present, the description should have explained paging semantics and it does not.

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?

The description restates the tool name ("bridge_inbox") wrapped in the vague verb "Execute", which does not say what the operation actually does — read an inbox, list messages, poll, or mutate state. "through the v2 service" adds a version reference but no resource or scope, and nothing distinguishes it from 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 Guidelines2/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 when another sibling (e.g. a listing or status tool) would be preferred. The agent is left to guess the tool's role from the name alone.

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