Skip to main content
Glama

Pause a BitFeed feed

pause_feed

Pause a feed so it will not deliver until resumed.

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>",
      "feed_id": "<feed_id>"
    },
    "name": "pause_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
feed_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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=false), and the description adds the meaningful trait that the pause is reversible and suppresses delivery until a resume. It does not say what happens to already-queued mail, whether the call is idempotent, or what errors arise on an already-paused feed.

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?

A single front-loaded sentence with no filler and no redundancy. It is efficient, though its brevity leaves the effect on queued messages unstated.

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 simple two-parameter state-change tool with annotations and no output schema, the core effect is conveyed. Missing pieces are the fate of undelivered/queued mail, idempotency on an already-paused feed, and any auth/ownership requirement for feed_id.

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?

The description mentions no parameters at all. With only 50% schema coverage, the undocumented feed_id must be inferred as "the feed to pause", while bitfeed_token's rich schema description does the rest of the work. The description adds no meaning beyond the schema.

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 ("Pause a feed") plus the effect ("will not deliver until resumed"), which makes the contrast with resume_feed inferable. It stops short of explicitly naming the sibling, so it is clear but not fully differentiated.

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 "until resumed" signals this is the reversible counterpart to resuming, and that delivery halts. There is no explicit when-to-use guidance, no preconditions (paused vs deleted, ownership/auth requirements), and no named alternative such as delete_feed for permanent stops.

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