Skip to main content
Glama

zk_solvency

Retrieve the current solvency proof to verify total reserves cover liabilities without exposing individual balances.

Instructions

Get the latest solvency proof — proves total reserves ≥ liabilities without revealing individual balances.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zk_solvency"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral property — the proof demonstrates reserves ≥ liabilities without revealing individual balances — but says nothing about freshness, whether the proof is generated on demand or cached, latency, or what the caller actually receives.

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?

A single front-loaded sentence gives the action first and then the guarantee it provides. Every clause earns its place, with no filler or repetition of the tool name.

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?

There is no output schema, no annotations, and no parameters, so the description is the only carrier of context — and it omits the return shape (a proof object? a timestamped attestation? a status?) and how the result relates to zk_proof_verify. Adequate to identify the tool, insufficient to predict its output.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Schema coverage is 100% but the schema is empty, so no additional compensation is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: fetch the latest solvency proof, and adds what the proof asserts (reserves ≥ liabilities). It is distinguishable from zk_proof_verify by the emphasis on retrieving the current proof, though it never names zk_proof_get, which sounds like the closest sibling.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, and no alternative such as zk_proof_get or zk_proof_verify is mentioned. The word 'latest' hints at the intended use case, but any routing decision between this and the other zk tools is left to inference.

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