Skip to main content
Glama

Manage my news sources

manage_news_sources
Destructive

YOUR custom news sources: the X handles and Telegram groups Gambit reads for you, and which of Gambit's curated news sources are on. Reads need api:read; changes need api:account and stay within your plan's caps (a full cap answers 403 tier_limit_exceeded — see get_plan_usage). action=list_x_handles: your handles (handle, is_news_source, name) and cap {tier, current, max, unlimited}. action=suggest_x_handles: handle suggestions for prefix (1-15 chars; limit 1-20), with already_tracked. action=add_x_handle / remove_x_handle: handle (with or without @); an add checks the handle exists on X (400 user_not_found_on_x when it does not). action=list_telegram_groups: your groups (id, title, username_or_invite, joined_at) and cap. action=add_telegram_group: identifier — a public @username, t.me link or invite link; Gambit's reader account joins and screens the group first, which can take ~20 s, and a rejected group is not added. action=remove_telegram_group: group_id from list_telegram_groups. action=toggle_news_source: switch one curated news source on or off for you (handle, included).

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": {
      "action": "<action>"
    },
    "name": "manage_news_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNosuggest_x_handles
actionYes
handleNoadd_x_handle, remove_x_handle, toggle_news_source
prefixNosuggest_x_handles
group_idNoremove_telegram_group
includedNotoggle_news_source: true turns the source on
identifierNoadd_telegram_group

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say destructive and not idempotent; the description adds real operational context: required scopes (api:read for reads, api:account for changes), plan caps with the exact 403 tier_limit_exceeded failure and a pointer to get_plan_usage, the X existence check returning 400 user_not_found_on_x, and the Telegram flow where Gambit's reader account joins and screens a group for ~20 s with rejected groups not added. That is substantial disclosure beyond what the annotations provide.

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?

Front-loaded with the one-sentence purpose, then a scannable semicolon-separated action:behavior mapping, which suits an eight-action enum tool. It is dense but nearly every clause carries information; slight cost is that the auth/cap sentence sits between the purpose and the action list, interrupting the action scan order.

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

Completeness5/5

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

For an eight-action mutation tool with no output schema, the description supplies the returned field sets for the list actions (handle, is_news_source, name; cap {tier, current, max, unlimited}; id, title, username_or_invite, joined_at), the auth and cap constraints, and the async screening caveat for Telegram adds. Nothing an agent needs to call any action correctly appears to be missing.

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

Parameters5/5

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

Schema coverage is already 86%, so the baseline would be 3, but the description adds genuine meaning: handle works with or without @, prefix is 1-15 chars and pairs with a 1-20 limit, group_id must come from list_telegram_groups, identifier accepts a public @username, t.me link or invite link, and included=true turns the source on. Each parameter is bound to its governing action rather than left generic.

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?

Opens with a specific resource statement ('YOUR custom news sources: the X handles and Telegram groups Gambit reads for you, and which of Gambit's curated news sources are on') and then enumerates all eight actions with concrete verbs (list, suggest, add, remove, toggle). An agent can distinguish this configuration tool from read-side siblings like get_news_feed and get_news_headlines without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Each action carries the condition that selects it ('group_id from list_telegram_groups', 'handle (with or without @)', 'switch one curated news source on or off for you'), which is effectively per-action routing guidance. It also points to get_plan_usage when a cap is hit. What is missing is an explicit statement of when NOT to use this tool (e.g., to read articles, use the news feed siblings), so it stops short of full alternative routing.

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