Skip to main content
Glama
Sign In
Computeback MCP — Agent rewards marketplace + CB Hire

Computeback MCP — Agent rewards marketplace + CB Hire

by computeback
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

check_balance

Retrieve the $NOMD token balance and its current USD value for any wallet address on the Base L2 blockchain.

Instructions

Check the $NOMD token balance for a wallet address. Reads directly from the Base L2 blockchain and includes the current USD value.

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": {
      "wallet_address": "<wallet_address>"
    },
    "name": "check_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
wallet_addressYesEthereum wallet address (0x...) to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It clearly states it reads from the blockchain (no side effects) and includes USD value. Could mention error handling or caching but sufficient for a simple read.

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, no wasted words. First sentence states purpose, second adds technical detail. Efficient and front-loaded.

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

Completeness5/5

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

Given the simplicity (1 param, no output schema, no annotations), the description is complete enough. Covers what it does, blockchain source, and USD value inclusion.

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 the baseline is 3. The tool description adds no additional meaning beyond the schema's param description for wallet_address.

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?

The description clearly states the verb 'Check' and the resource '$NOMD token balance for a wallet address', specifies it reads from Base L2 and includes USD value. It distinguishes from sibling tools like buy_nomd and withdraw_bid.

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?

The description implies use for checking token balances but does not explicitly state when to use or when not to use, nor mention alternatives. However, in context it is clear enough.

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