Skip to main content
Glama

BitFeed mailbox

get_mailbox
Read-only

List or fetch mailbox items (payloads stored when a webhook is not used or has failed). Items are kept for 72 hours.

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

Input Schema

NameRequiredDescriptionDefault
feed_idNo
item_idNoOptional. Fetch one mailbox item.
bitfeed_tokenYesBitFeed account token (btf_…). Also accepted as Authorization: Bearer. Omit on the first create_feed to open an account; the token is returned once.
include_ackedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — a 72-hour retention window — but says nothing about ordering, paging, result limits, or whether listing is affected by acknowledgement state.

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

Conciseness4/5

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

Two short sentences with no filler; the list/fetch duality and the retention limit are front-loaded. Slightly more structure (e.g., separating the fetch-by-item_id mode) would help, but nothing is wasted.

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

Completeness3/5

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

For a 4-parameter, read-only tool with no output schema, an agent still lacks the meaning of include_acked, the default listing scope, and any indication of ordering or volume of returned items. Retention is covered well; the rest is left to the schema's silence.

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

Parameters2/5

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

Schema coverage is only 50%: feed_id and include_acked have no descriptions, and include_acked (default false) is the parameter whose meaning most affects results. The description does not clarify what acknowledged items are, whether they are filtered by default, or how feed_id interacts with item_id; it only implies the single-item fetch mode.

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?

The description names a specific verb pair and resource ('List or fetch mailbox items') and clarifies what a mailbox item actually is — payloads stored when a webhook is absent or failed. It is clear enough to distinguish a read of stored payloads from feed-level operations, though it never explicitly contrasts itself with the ack_mailbox sibling.

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

Usage Guidelines3/5

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

The parenthetical gives the circumstance that produces mailbox items, which implies when they matter (webhook not configured or delivery failed). However, there is no explicit when-to-use/when-not-to-use statement and no mention of ack_mailbox as the follow-up path or as an alternative for already-consumed items.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources