Skip to main content
Glama

Vault state

get_vault
Read-only

Live state of the HITZ Sovereign Vault: each pool's reserves, HITZ price, current fee and dislocation, USD values, and the HITZ Event Horizon (the most HITZ an account can hold and still send it anywhere).

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": "get_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine behavioral context beyond that: the data is 'Live' current state (freshness), values are denominated in USD as well as token terms, and it defines the non-obvious 'HITZ Event Horizon' concept inline. It does not mention refresh cadence, staleness, or whether the call hits the chain directly, so it is not a 5.

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 that names the resource first and then enumerates return contents compactly. Because there is no output schema, every listed item earns its place, and there is no filler or repetition of the title.

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?

With no parameters and no output schema, the description carries the full burden of describing what comes back, and it does enumerate the returned fields in reasonable detail. It omits the shape/units of the returned values (e.g. decimals, per-pool nesting) and any freshness guarantee, which is a modest gap for a state-read tool but not a blocking one.

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 and the baseline of 4 applies. No misleading parameter information is present.

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 resource (the HITZ Sovereign Vault) and enumerates exactly what state is returned: pool reserves, HITZ price, fee, dislocation, USD values, and the Event Horizon. An agent can tell this is a read of vault/pool state rather than an account, transaction, or swap-building tool. It stops short of explicitly naming a sibling it is distinct from, which keeps it at 4 rather than 5.

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?

Usage is only implied: an agent infers it should call this to inspect current vault/pool conditions before quoting or swapping. There is no explicit when-to-use statement, no mention of whether this is the authoritative source versus the sibling 'quote' tool, and no exclusions or prerequisites. Adequate but leaves the routing decision to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.