Skip to main content
Glama

Update a BitFeed feed

update_feed

Patch interval, trigger, params, webhook_url or mailbox on an existing feed.

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": "update_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
feed_idYes
mailboxNo
triggerNoTrigger object when mode is trigger. type is one of btc_move (percent, optional window_seconds), btc_threshold (above and/or below in USD), weather_alert (location), airport_delay (airport, optional min_delay_minutes), sec_filing (symbol, optional forms; default 8-K, 10-Q, 10-K; endpoint stock_filings). Optional max_fires, expires_at, cooldown_seconds.
intervalNo
webhook_urlNo
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.
interval_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / trigger / description
      Previous value: -"Trigger object when mode is trigger. type is one of btc_move (percent, optional window_seconds), btc_threshold (above and/or below in USD), weather_alert (location), airport_delay (airport, optional min_delay_minutes). Optional max_fires, expires_at, cooldown_seconds."New value: +"Trigger object when mode is trigger. type is one of btc_move (percent, optional window_seconds), btc_threshold (above and/or below in USD), weather_alert (location), airport_delay (airport, optional min_delay_minutes), sec_filing (symbol, optional forms; default 8-K, 10-Q, 10-K; endpoint stock_filings). Optional max_fires, expires_at, cooldown_seconds."
  2. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, non-open-world mutation, so the safety profile is covered for free. The description adds the useful implication that only supplied fields are patched, but leaves out what happens to unspecified fields, whether trigger changes interact with a mode setting, and error/validation behavior.

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 zero padding and the field list up front. It is efficient, though the terseness is arguably what leaves the semantic gaps noted above.

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

Completeness2/5

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

For an 8-parameter mutation tool with a nested trigger object, 25% schema coverage and no output schema, the description is too thin. An agent cannot tell from it how interval and interval_seconds differ, what mailbox toggles, or whether omitted fields are cleared or preserved.

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 25%, so the description carries real weight here, yet it merely names fields rather than explaining them. It never mentions interval_seconds at all, gives no meaning for the mailbox boolean, and says nothing about the shape of params, leaving the interval/interval_seconds relationship ambiguous.

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 ("Patch") and resource ("existing feed") and enumerates the five mutable fields, which distinguishes it from create_feed and delete_feed by inference. It stops short of naming those siblings explicitly, so differentiation relies on the reader's knowledge of the catalog.

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?

"on an existing feed" implies the precondition that the feed must already exist, and "Patch" implies partial update, so the usage context is inferable. There is no explicit when-to-use vs. alternatives guidance (e.g., create_feed for new feeds, pause_feed for toggling state) and no mention of permission or token requirements.

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