Skip to main content
Glama

Account

get_account
Read-onlyIdempotent

One address’s ETH, Semiosis, stake (sSemiosis), votes and delegate, Citizen Pass, allowances to the protocol’s contracts and open loans. Read-only.

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": {
      "address": "<address>"
    },
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesA Robinhood Chain address: 0x and 40 hex digits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered and the trailing 'Read-only' adds nothing. What the description does contribute is the only signal about return content — no output schema exists, so enumerating balances, stake, votes, delegate, Citizen Pass, allowances and loans is genuinely useful behavioral disclosure. It omits behavior for unknown/unfunded addresses and any data-freshness caveat.

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 the substantive content front-loaded; every listed item is informative rather than filler. The closing 'Read-only' is redundant with readOnlyHint and is the one phrase that does not earn its place.

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 aggregator with no output schema, the description carries return-shape information adequately by listing all the account facets. Minor gaps remain — whether unknown addresses error or return empty, and whether results are snapshot-at-latest-block — but nothing essential to invoking it correctly is 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?

Schema description coverage is 100% and the single 'address' parameter is fully documented in the schema, including the 0x-plus-40-hex pattern. The description adds no format, chain, or validation detail beyond that, so the baseline of 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 ('One address') and enumerates exactly what is returned: ETH, Semiosis, stake/sSemiosis, votes and delegate, Citizen Pass, allowances and open loans. That enumeration distinguishes it clearly from siblings like get_contracts, get_duties and get_proposals, which each cover a different slice. It stops short of a full verb-plus-resource statement ('get the full account snapshot'), so it is strong rather than exemplary.

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 field list tells an agent this is the one-call overview of everything an address holds, which suggests calling it before drilling into get_duties or get_proposals. There is no explicit when-to-use/when-not statement and no named alternative, so the routing signal has to be inferred from the returned-content list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources