Returns the current Strale wallet balance. Call this before executing paid capabilities to verify sufficient funds, or after a series of calls to reconcile spend. Returns balance in EUR cents (integer) and formatted EUR string. Requires an API key — returns an auth instruction if none is configured.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses return format ('EUR cents (integer) and formatted EUR string'), authentication needs ('Requires an API key'), and error behavior ('returns an auth instruction if none is configured'). This is strong transparency for a simple read-only tool, though it stops short of mentioning potential rate limits or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, front-loaded with the core purpose, then usage guidance, then output details and auth note. Every sentence adds value, and the structure is logical and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a simple, parameterless tool. The description covers its purpose, when to use it, return format, and authentication requirement. Since there is no output schema, the description adequately informs the agent about what to expect. It is fully sufficient for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline for this dimension is 4. The description doesn't need to explain parameter semantics, and it correctly focuses on output and usage rather than inventing unnecessary parameter details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Returns the current Strale wallet balance.' This is a specific verb+resource combination that distinguishes it from sibling tools like strale_transaction or strale_execute, which involve different operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit usage context: 'Call this before executing paid capabilities to verify sufficient funds, or after a series of calls to reconcile spend.' It doesn't explicitly name alternatives, but the guidance is clear and actionable, warranting a 4 rather than a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool addresses a distinct function: balance checks, capability execution, onboarding, methodology docs, connectivity, registry search, transaction history, trust profiling, and on-chain assurance. There is no overlap or ambiguity between tool purposes.
All tools follow the consistent pattern of a 'strale_' prefix with lowercase snake_case names (e.g., strale_balance, strale_getting_started). The naming is uniform and predictable across the entire set.
With 9 tools, the server is well-scoped for its purpose of exposing core interactions with a 290+ capability API. It avoids bloat while providing all necessary operations without being too sparse.
The tool surface covers the full lifecycle: discovery (strale_search), execution (strale_execute), financial management (strale_balance), audit (strale_transaction), trust evaluation (strale_trust_profile), specialized on-chain checks (strale_web3_assurance), plus support functions (getting_started, ping, methodology). No obvious gaps exist.
