Skip to main content
Glama

Create a BitFeed (prepaid)

create_feed

Create a scheduled or trigger feed. Omit bitfeed_token to open a new prepaid account; the response includes a btf_ token that is not shown again. Delivery is a webhook and/or mailbox. Each delivery costs the same as a normal call to that endpoint. Top up with the topup tool before the feed can deliver. Docs: https://api.bittuitive.ai/data/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": {
      "endpoint": "<endpoint>",
      "mode": "<mode>"
    },
    "name": "create_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
paramsNoEndpoint params, e.g. {location} or {airport} or {symbol}.
mailboxNoStore deliveries in the mailbox (default true).
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.
endpointYesDirect endpoint, e.g. btc_price, btc_price_lite, weather_now, weather_alerts, airport_delays, stock_filings.
intervalNohourly, daily, or a number of seconds (schedule mode).
webhook_urlNohttps webhook URL. A signing secret is returned once.
bitfeed_tokenNoBitFeed 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. Changed2 schema fields changed
    • changedInput schema / properties / endpoint / description
      Previous value: -"Direct endpoint, e.g. btc_price, weather_alerts, airport_delays."New value: +"Direct endpoint, e.g. btc_price, btc_price_lite, weather_now, weather_alerts, airport_delays, stock_filings."
    • 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

A4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that omitting the token opens a new prepaid account, that the returned btf_ token is shown only once, that delivery can be by webhook and/or mailbox, and that each delivery is billed like a normal endpoint call. It stops short of explaining failure modes or rate limits, but it adds substantial behavioral context.

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?

The description is front-loaded with the purpose and then gives only high-value operational details: prepaid account behavior, one-time token, delivery channel, per-delivery cost, and top-up prerequisite. The documentation link is also useful rather than wasteful.

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 complex creation tool with nine parameters, nested trigger configuration, and no output schema, the description covers the critical prepaid, billing, token, and delivery model well. The main remaining gap is that the response shape beyond the one-time token is not described, so an agent still lacks a complete picture of what creation returns.

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

Parameters3/5

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

Schema coverage is 78%, so the parameter descriptions already carry most of the meaning. The description adds useful context for bitfeed_token omission and one-time token return, but it does not materially clarify mode, interval, endpoint, or nested trigger semantics beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Create a scheduled or trigger feed.' It also names the two supported modes, which lets an agent distinguish this creation tool from siblings such as update_feed, pause_feed, or delete_feed.

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 description gives important operational context such as omitting bitfeed_token on first use and topping up before delivery. However, it does not explicitly say when to use create_feed versus update_feed or request_data, so the agent must infer the surrounding workflow.

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