Skip to main content
Glama

SALT19 Agent Utility Grid

by io.github.GabrielAllit1

Base Wallet Balance

base-wallet-balance
Idempotent

Read a wallet's live native ETH balance on Base at the latest block without an API key. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes
_salt19_handoff_idNoOptional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry.
_salt19_operation_idNoOptional but recommended semantic purchase identifier preserved across challenge/payment/retries.
_x402_payment_signatureNoOptional x402 payment proof. Omit on the first call; include after satisfying the challenge.

TDQS

A4.1/5.0
Behavior4/5

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

Adds valuable behavioral context beyond annotations: the $0.01 x402 price, the no-API-key access path, and live-at-latest-block semantics. The annotation says readOnlyHint=false, but the disclosed payment side effect makes this non-contradictory; idempotent and destructive hints are already annotated.

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, front-loaded sentences with no filler. It states purpose, scope, pricing, and the key optional parameter in the minimum words needed.

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

Completeness3/5

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

Covers purpose, scope, price, and no-API-key access, but does not describe the full x402 challenge/payment flow or the output format/units, and there is no output schema to fill that gap. The schema hints at the challenge flow, but return semantics remain underspecified.

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 already documents three optional protocol parameters with clear descriptions; the description adds that address is the wallet being queried and that _salt19_operation_id is recommended but optional. With 75% schema coverage, it compesates only partially for the undocumented address parameter.

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?

States a specific verb and resource: 'Read a wallet's live native ETH balance on Base at the latest block'. The 'native ETH' qualifier clearly distinguishes it from sibling token/allowance/state tools, so an agent can select it confidently.

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?

Gives clear context: use when you need a native ETH balance on Base with no API key and are willing to pay via x402. It doesn't name alternatives explicitly, but 'native ETH' implicitly excludes token-balance and transaction-status tools.

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

All SALT19 Agent Utility Grid toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Multiple tools occupy the same decision space: agent-decision-preflight, dependency-go-no-go, repo-adoption-go-no-go, github-repo-preflight, and npm-package-intel all target install/adopt GO/WARN/BLOCK decisions with overlapping scope. Discovery tools like find-salt19-tool and salt19-pricing also blur together. Descriptions are detailed, but the boundaries between these tiers are not obvious enough for reliable agent selection.

Naming Consistency3/5

Names consistently use lowercase hyphenated tokens and domain prefixes, which gives some predictability. However, styles are mixed: some tools are verb-led (find-, report-, verify-), while others are noun-headed (github-repo-facts, salt19-pricing, nws-active-alerts), and product-tier suffixes like -preflight, -facts, -intel, and -go-no-go are applied inconsistently. The naming is readable but does not follow a single clear pattern.

Tool Count2/5

33 tools is well above the range where a toolset remains easy to navigate, even for a broadly scoped utility grid. The count includes multiple free routing/telemetry tools plus many paid data and decision tools, making the surface feel heavy. A more consolidated tiered design would reduce selection burden.

Completeness4/5

The server covers a wide range of claimed capabilities: live state/facts for Base, GitHub, npm, SEC, NWS, USGS, and URL; bounded decisions for dependencies, repos, plans, code changes, and commerce; plus x402 payment support and receipt verification. Minor gaps exist around actually executing payments or settlements, but that seems intentionally out of scope for a non-custodial utility grid.

Resources