Skip to main content
Glama

Acknowledge a BitFeed mailbox item

ack_mailbox

Mark a mailbox item as acked so it is hidden from the default list.

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>",
      "item_id": "<item_id>"
    },
    "name": "ack_mailbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare a non-read, non-destructive, closed-world mutation, and the description usefully adds the actual effect (the item is hidden, not deleted) and the qualifier 'default list', implying other views still show it. It does not state reversibility, required token permissions, or the response, so it adds context without fully covering behavior.

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?

A single front-loaded sentence that states the action and its effect with zero filler. Every clause earns its place.

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 two-parameter mutation with no output schema, the description covers the state change but omits how to undo it, what the call returns, and the format of the undocumented item_id. Adequate but with visible gaps.

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%: bitfeed_token is documented in the schema, but item_id has no description anywhere, and the description does not say what an item ID looks like or where to obtain it (presumably from get_mailbox). The description adds no parameter meaning at all.

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 gives a specific verb and resource ('mark a mailbox item as acked') plus the observable consequence ('hidden from the default list'), which clearly separates it from the read-only get_mailbox sibling. It stops short of naming an alternative, but the action is unambiguous.

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?

Usage is only implied: the phrase 'so it is hidden from the default list' hints at when an agent would ack rather than fetch. There is no explicit guidance on prerequisites, whether the action can be undone, or how to retrieve acked items via get_mailbox.

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