Skip to main content
Glama
Sign In
@proof-holdings/mcp-server

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

poll_chat_id_discovery

Read-only

Polls a chat ID discovery token to retrieve the Telegram chat ID, user ID, and username once the user interacts with the bot.

Instructions

Poll a chat ID discovery token. Returns the discovered Telegram chat ID, user ID, and username once the user interacts with the bot.

Before calling this for a challenge you created, make sure your reply text already shows the user what to act on — the link itself, the SMS text and number, or a note to check their inbox; a link that appeared only in a tool result is one they never saw.

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

Input Schema

NameRequiredDescriptionDefault
tokenYesDiscovery token from create_chat_id_discovery

Output Schema

NameRequiredDescriptionDefault
statusNo
chat_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "chat_id": {},
+    "status": {}
+  },
+  "type": "object"
+}
  2. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds substantive behavior beyond that — the token resolves only after the user interacts with the bot, an auth prerequisite exists, and there is an explicit constraint that the link/text must appear in the agent's reply rather than only in tool output. It stops short of saying whether the call blocks or returns an empty status while pending.

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?

Purpose is front-loaded, followed by the user-visibility caveat and then the access prerequisite, with no filler. The access paragraph is procedural but genuinely necessary since the tool is unusable without it.

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?

An output schema covers return values, so the description needn't enumerate them, and it still summarizes them. Between the auth prerequisite, the pending-until-interaction semantics, and the user-visible-output warning, an agent has what it needs to call this correctly.

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?

The single token parameter is fully documented in the schema (100% coverage, sourced from create_chat_id_discovery). The description adds nothing about token lifetime or what happens when a token is expired or reused, so this is baseline.

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 and resource ("Poll a chat ID discovery token") and names what comes back (chat ID, user ID, username). It does not, however, distinguish itself from the closely named sibling wait_for_chat_id_discovery, which an agent could easily confuse with it.

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?

Gives real context: use it for a challenge you created, and it requires a Proof account with PROOF_API_KEY set. But it never says why to poll instead of calling wait_for_chat_id_discovery, which is the most likely selection decision an agent faces here.

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