Skip to main content
Glama

Resume a BitFeed feed

resume_feed

Resume a paused feed. Fails if the prepaid balance is zero or the feed has expired.

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": "resume_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

A3.6/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, non-destructive, not open-world); the description adds the real behavioral facts an agent needs — the operation mutates feed state and hard-fails on zero balance or expiry. It does not say whether resuming is idempotent or what happens to queued data, but it goes meaningfully beyond the structured fields.

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?

Two short sentences with zero filler; the purpose is front-loaded and the failure condition follows immediately. Nothing is repeated from the title or schema.

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?

For a simple two-parameter state-transition tool with no output schema, the description covers purpose plus the two blocking preconditions, which is enough to call it correctly. A note on whether the call is idempotent or what state the feed returns would complete it.

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 description coverage is only 50%: bitfeed_token is well documented (including the Authorization: Bearer alternative and the create_feed bootstrap case), but feed_id is bare. The description mentions no parameters at all, so it does nothing to close that gap for feed_id.

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 uses a specific verb and resource ('Resume a paused feed'), which is unambiguous and implicitly the inverse of the sibling pause_feed. It does not explicitly name alternatives, but the action is distinct enough that an agent can select it without opening the schema.

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?

It gives one when-not condition ('Fails if the prepaid balance is zero or the feed has expired'), which is useful pre-call guidance. It stops short of telling the agent what to do instead in those cases (e.g. call topup or create_feed), so the routing guidance is implied rather than explicit.

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