Skip to main content
Glama

Vault status

vault_status

Reports registered datasets, remaining reveal budget, current mode, and ledger verification status so agents can confirm the sealed store is ready for held-out scoring.

Instructions

Registered datasets, reveal budget, mode, and whether the ledger verifies.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
modeYes
noteYes
spentYes
budgetYes
projectYes
datasetsYes
ledger_okYes
remainingYes
ledger_headYes
ledger_entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the burden: it does disclose that the tool reports a verification result ('whether the ledger verifies'), implying a read-only diagnostic with a pass/fail signal, which is meaningful behavioral context. It omits any statement of cost, side effects, or failure behavior, but for a zero-parameter read it adds reasonable value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one short fragment with no wasted words, but the fragment style with terms like 'reveal budget' and 'mode' is cryptic and lacks the framing clause that would make it immediately parseable. Brevity here borders on under-specification rather than efficiency.

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?

An output schema exists, so return values need not be detailed, and the description reinforces their themes; the tool is simple and parameter-free. What is missing is the framing an agent needs to pick this over dashboard: what 'mode' and 'reveal budget' mean and when this check is the right call.

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 no parameters, so there is no parameter semantics to explain; the baseline applies. The listed items are return content, not inputs, so they do not compensate for a gap that does not exist.

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

Purpose3/5

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

The description is a noun-phrase list of the fields returned (datasets, reveal budget, mode, ledger verification) rather than a verb+resource statement, so the actual purpose ('return current vault status') is only inferable from the title. It does indicate the tool's content scope, which distinguishes it from siblings like score or evaluate, but the agent must bridge the gap itself.

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?

There is no when-to-use guidance, no mention of alternatives such as dashboard or audit_claims, and no stated preconditions. The agent is left to infer that this is the general health/state check.

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