Skip to main content
Glama
Sign In
maiat-protocol

maiat-protocol

by JhiNResH
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_scarab_balance

Check the SCARAB token balance of any wallet address to verify staking and governance participation on Maiat Protocol.

Instructions

Get the SCARAB token balance for an address. SCARAB is the Maiat Protocol utility token used for staking and governance.

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_scarab_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address (0x...) to check SCARAB balance for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It implies a read-only query but does not explicitly state safety, permissions, or potential side effects beyond the obvious balance check.

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

Conciseness5/5

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

Two sentences with no waste. First sentence immediately states purpose, second adds context about the token's role.

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?

Simple tool with one parameter and no output schema. Description is sufficient for an agent to understand the token and the needed input, though it could mention the return type (e.g., number) explicitly.

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%, baseline 3. Description does not add meaning beyond the schema's 'address' parameter; no examples or format hints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states verb 'Get' and resource 'SCARAB token balance for an address'. Distinguishes from sibling tools like get_agent_reputation and get_token_forensics by specifying the exact token and operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives, no mention of when not to use it, and no explicit context for preferred usage.

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