Skip to main content
Glama
Sign In

Provian

by ai.provian
OverviewDiscussionsAdmin

get_pvt_balance

Read YOUR agent wallet's on-chain balances — PVT (the live PVT9 balance), ETH, and USDC — via the relay. Self-scoped: an agent reads only its own wallet. Requires agent API credentials + wallet_id.

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_id": "<wallet_id>"
    },
    "name": "get_pvt_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
wallet_idYesYour agent wallet id (wallet_aw_…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 and does well: it discloses that this is a read operation, that it goes through a relay, that it is self-scoped (no reading other wallets), and that it requires auth credentials plus wallet_id. It does not describe rate limits, failure modes, or the response shape, so it stops just short of full transparency.

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 tight sentences: the first states exactly what is returned, the second front-loads the key scope and prerequisite constraints. No filler or redundant restatement of the tool name.

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 single-parameter read tool with no output schema, the description covers purpose, scope, auth prerequisites, and the referenced data. The main remaining gap is that it does not describe the return structure (e.g., whether balances are strings or amounts, per-chain detail) despite there being no output schema to cover it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100% and the schema documents wallet_id with the wallet_aw_ prefix format. The description reinforces the required meaning by stating it must be the caller's own wallet, which adds a semantic constraint (self-scoping) beyond the schema's bare type definition.

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 names a specific verb (read) and specific resources (PVT, ETH, USDC on-chain balances) scoped to the agent's own wallet, and it explicitly distinguishes itself from balance-related siblings like get_pvt_estimate by noting the live PVT9 balance. An agent can tell what this returns without opening any schema.

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

Usage Guidelines4/5

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

It states a clear usage context: an agent reads only its own wallet, self-scoped, and it requires agent API credentials plus wallet_id. It does not explicitly name when to prefer get_pvt_estimate over this tool, but the self-scoped/on-chain framing gives enough context to choose correctly.

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

All Provian toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources