Skip to main content
Glama
Sign In
telegraph-mcp

telegraph-mcp

Official
by telegraphprotocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Account

telegraph_account
Read-only

Look up USDC and ETH balances plus Telegraph escrow funds (spendable, deposited, debt, pending withdrawal) for any wallet address or the server's own wallet.

Instructions

This server's wallet (or any address): wallet USDC and ETH, and the Telegraph escrow balance that pays for asks (spendable, deposited, debt, pending withdrawal). Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "telegraph_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoAddress to look up. Default: this server's wallet.

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 already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond that by disclosing the exact return contents, including the escrow sub-balances (spendable, deposited, debt, pending withdrawal) that pay for asks, and confirming the call is free.

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 dense sentence plus 'Free.' — every clause carries information (default target, wallet balances, escrow breakdown, cost). It is slightly telegraphic and omits a leading verb, but nothing is wasted and the key scope is front-loaded.

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 zero-required-parameter read tool with annotations and no output schema, this is nearly complete: it covers the default target, the returned fields, and the cost. The only gap is that it doesn't explain what happens for an unregistered or invalid address.

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 address parameter is fully documented in the schema, including the 'defaults to this server's wallet' behavior, which the description echoes. The description adds no syntax or format detail beyond the schema, 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?

The description names the resource (this server's wallet or any address) and enumerates exactly what is returned: wallet USDC and ETH plus the Telegraph escrow balance broken into spendable, deposited, debt, and pending withdrawal. It lacks an explicit verb like 'get' or 'look up', and it doesn't name a sibling it differs from, but an agent can tell this is the balance-inspection tool from the enumerated fields alone.

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?

It gives an implicit usage cue by noting the address is optional and defaults to this server's wallet, and the word 'Free' signals it costs nothing versus paid siblings like telegraph_ask. However, it never states when to prefer this over telegraph_deposit or the ask tools, and there are no explicit exclusions.

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