Skip to main content
Glama
Sign In
mq-bridge

mq-bridge

by marcomq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

route_messages

Destructive

Returns recent messages captured on a route, newest last. Each message is delivered once, so repeated calls yield only what arrived since the previous read.

Instructions

Return the most recent messages captured on a route, newest last. Only routes started with capture_last capture anything. Reads are destructive: each message is returned once, so repeated calls yield only what arrived since the last call.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe route name, as returned by `start_route` or listed by `list_routes`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • changedInput schema / properties / name / description
      Previous value: -"The route name."New value: +"The route name, as returned by `start_route` or listed by `list_routes`."
  2. First observedv1.0.3

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the destructiveHint annotation by explaining the actual mechanism: messages are consumed on read, so each message is returned once and repeated calls yield only what arrived since. That is exactly the operational detail an agent needs to avoid silently losing data, and it is consistent with readOnlyHint=false / destructiveHint=true.

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

Conciseness5/5

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

Three short sentences, front-loaded with what the tool returns, followed by the capture precondition and the destructive-read warning. No sentence is filler.

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?

With no output schema, the description still conveys ordering ('newest last') and the consumption semantics, covering the critical behaviors. It stops short of describing what a message record contains (fields, size, truncation), which is the one remaining gap for a tool whose return shape is otherwise undocumented.

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?

Only one parameter and schema coverage is 100%, with the schema itself documenting the route name and its provenance from start_route/list_routes. The description adds no syntax, casing, or format detail beyond the schema, so the baseline of 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Return the most recent messages captured on a route') plus the ordering ('newest last'). It does not explicitly contrast with the closest sibling, wait_route, so the agent must infer the difference from the capture_last prerequisite rather than being told.

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

Usage Guidelines4/5

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

Gives a concrete prerequisite for the tool to return anything ('Only routes started with `capture_last` capture anything') and warns that repeated calls yield only new messages, which shapes usage. There is no explicit when-to-use-this-vs-wait_route guidance or exclusion statement.

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

Deploy Server

Other Tools