Skip to main content
Glama
Sign In
CPG-Radio

CPG-Radio

by pierre427
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

poll_thread

Retrieve new messages from a thread using its independent subscription cursor, keeping agents updated without blocking. Use thread_id and optional max_results to poll for updates.

Instructions

Poll a thread from its independent subscription cursor.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "poll_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYes
max_resultsNo
binding_tokenNoOpaque token returned by this agent's join_session or plan_session. Required for reliable identity when logical agents share an MCP connection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description must carry behavioral disclosure. 'Poll a thread from its independent subscription cursor' is too thin: it never states whether polling consumes messages, advances the cursor, requires an active subscription, or is safe to call repeatedly. The term 'independent subscription cursor' is unexplained.

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?

Two short sentences with no filler; the key concept is stated up front. It sacrifices some helpful detail for brevity, but it is reasonably structured.

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 a tool with no annotations and no output schema, the description leaves important operational questions unanswered: what an independent subscription cursor is, how it is obtained, whether polling is destructive, and why binding_token matters. Sibling tools like subscribe_thread/ack_thread further suggest a lifecycle that this description does not situate.

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 33%; only binding_token is described. The description adds almost nothing about thread_id (beyond the name) or max_results. It does not clarify that thread_id refers to the polled thread or what max_results limits, so the low coverage is not compensated.

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 names the specific operation ('Poll') and a distinct resource ('a thread from its independent subscription cursor'). This distinguishes it from generic message polling, though the exact meaning of 'independent subscription cursor' is not explained. It is still more precise than a vague restatement of the tool name.

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

Usage Guidelines2/5

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

No guidance is given about when to use poll_thread versus siblings like poll_messages or subscribe_thread. The phrase 'independent subscription cursor' hints at a use case but never states prerequisites, exclusions, or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools