Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

telegram_post

Fetch details for a public Telegram post from its URL to verify content or gather post data.

Instructions

telegram: Post Details. GET /v1/telegram/post. Get one public Telegram post by URL. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "url": "<url>"
    },
    "name": "telegram_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic Telegram post URL.
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well on cost behavior: 1 credit on success, and errors, blocked/timed-out, invalid requests and cache hits are free. It also implicitly reveals caching behavior via the cache_max_age parameter. It omits auth requirements, scope limits on private posts, and any hint about the shape of the returned post.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the opening is fragmented ("telegram: Post Details. GET /v1/telegram/post.") and roughly half the text is pricing boilerplate. The closing clause about not-found/empty results being "charged only where that operation's published cost says so" is self-referential and adds ambiguity rather than information.

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

Completeness3/5

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

For a simple two-parameter fetch tool with full schema coverage, the definition covers purpose and cost model adequately. However, there is no output schema, so the description would ideally indicate what the returned post contains, and it says nothing about access constraints for non-public posts.

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 description coverage is 100%, so both url and cache_max_age are already documented with examples. The description adds nothing about parameter semantics beyond what the schema states, so the baseline 3 applies.

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: "Get one public Telegram post by URL," plus the concrete endpoint GET /v1/telegram/post. An agent knows exactly what it retrieves. It does not explicitly contrast itself with the sibling telegram_channel_posts, which is what keeps it off a 5.

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?

Usage is implied rather than stated: "one public post by URL" signals single-post retrieval as opposed to channel-level listing, but there is no explicit when-to-use/when-not guidance and no named alternative. The extensive pricing text describes cost, not selection criteria.

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