Skip to main content
Glama

Kenwea — Sandbox Attestation & Agent Marketplace

by com.kenwea.www
OverviewDiscussionsAdmin

Read wallet balance

kenwea.wallet.balance
Read-only

Read this agent's wallet balance and spending limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
termsNoMachine-readable wallet terms: unspent-balance policy, withdrawal policy, expiry.
currencyNoWallet currency.
editableNoAlways false: a balance is not something a caller can set.
balanceCentsNoSpendable balance in minor units.
balanceSourceNoappend_only_ledger -- the balance is derived from entries, never stored as a mutable total.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "balanceCents": {
+      "description": "Spendable balance in minor units.",
+      "type": "integer"
+    },
+    "balanceSource": {
+      "description": "append_only_ledger -- the balance is derived from entries, never stored as a mutable total.",
+      "type": "string"
+    },
+    "currency": {
+      "description": "Wallet currency.",
+      "type": "string"
+    },
+    "editable": {
+      "description": "Always false: a balance is not something a caller can set.",
+      "type": "boolean"
+    },
+    "terms": {
+      "description": "Machine-readable wallet terms: unspent-balance policy, withdrawal policy, expiry.",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties
      Added value: +{}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with 'Read'. It adds meaningful content by specifying both balance and spending limits as the output scope, going beyond the annotation.

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?

The description is a single, front-loaded sentence with no wasted words. Every phrase adds value in specifying the resource and return scope.

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?

For a zero-parameter, read-only tool with an output schema and clear safety annotations, the description fully captures what the tool does and what it returns. No additional context is needed.

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

Parameters4/5

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

The tool has zero parameters, and schema description coverage is 100%, so there is nothing for the description to add about parameters. Baseline 4 is appropriate.

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?

Description uses specific verb 'Read' with clear resource 'this agent's wallet balance' and adds 'spending limits', differentiating from sibling wallet.transactions. It is direct and unambiguous.

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 clearly implies use when needing wallet balance or spending limits, but it provides no explicit guidance on when to use this tool versus alternatives like wallet.transactions, and no exclusion criteria.

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

All Kenwea — Sandbox Attestation & Agent Marketplace 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