Skip to main content
Glama
Sign In
telegraph-mcp

telegraph-mcp

Official
by telegraphprotocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Intent details

telegraph_intent
Read-only

Retrieve details for a Telegraph AI intent, including its kind, request parameters, response fields, and top-ranked miners, to plan or validate agent inference calls.

Instructions

One intent: its kind (deterministic, hybrid or judgment), the params an ask can send, the fields the answer comes back in, and its top-ranked miners. Free.

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": {
      "intent": "<intent>"
    },
    "name": "telegraph_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYesIntent name, e.g. WEATHER_CHECK_TEMPERATURE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower, and the description still adds non-schema context: the call is "Free" and the response is structured into intent kind, accepted params, answer fields, and top miners. It stops short of stating behavior for an unknown intent name, which is a real gap given there is no output schema.

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?

One densely packed sentence with zero filler, front-loaded on the resource. The colon-separated enumeration is readable, though the phrase "its kind (deterministic, hybrid or judgment)" is heavier than needed for a lookup tool.

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 one-parameter read tool with no output schema, the description compensates well by enumerating the fields the answer comes back in, plus cost and miner ranking. Only the failure/not-found case and the relationship to the ranking and ask tools are missing.

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?

With a single parameter at 100% schema description coverage, the schema already explains that the argument is an intent name with an example. The description adds no further meaning about naming, case sensitivity, or lookup failure, so 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?

"One intent" plus an enumeration of the returned facets (kind, params, answer fields, top-ranked miners) makes the resource and its content unambiguous. It is clearly a single-intent metadata lookup, but it never names the sibling that lists or searches intents (telegraph_find_intents), so the differentiation is left to inference.

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 only implied: the phrase "the params an ask can send" hints this is a pre-flight lookup before telegraph_ask, but the description never states when to call this instead of telegraph_find_intents or telegraph_ask. There are no exclusions or prerequisites, so an agent must infer the workflow position.

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