Skip to main content
Glama

Vault dashboard

dashboard

View scoring budget, ledger, recent sealed scores, refusals, and workspace findings in one summary, and compare reported metrics against sealed scores to spot gaps.

Instructions

Budget, ledger, recent sealed scores, refusals, workspace findings, and the gap between the agent's own numbers and the sealed scores. Renders as an MCP App where supported; the summary field carries the same information as text. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
gapsYesThe agent's own best number vs the latest sealed score
modeYes
spentYes
budgetYes
scoresYesRecent sealed scores, oldest first
projectYes
summaryYesPlain-text version of everything below, for clients without Apps
findingsYesCurrent workspace findings
refusalsYes
ledger_okYes
remainingYes
ledger_headYes
ledger_entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 usefully discloses the dual rendering path (MCP App where supported, with the `summary` field carrying the same content as text) and that invocation is free, but it never states whether the call is read-only or has side effects — notable given that siblings include write-like operations such as audit_claims and evaluate.

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

Conciseness4/5

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

Two sentences, no filler, with the content inventory front-loaded and the rendering caveat immediately after. The opening noun list is slightly telegraphic but efficient.

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?

An output schema exists and the tool takes no parameters, so the description need not explain return values; what it must convey — what the dashboard surfaces and how it renders in non-App clients — it does. Only the read-only/mutation question remains unaddressed.

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 applies. The only parameter-adjacent fact an agent might want — the `summary` field in the result — is mentioned in passing.

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?

The description enumerates concrete contents (budget, ledger, sealed scores, refusals, workspace findings, agent-vs-sealed gap) plus a rendering mode, which is enough to tell this apart from vault_status or evaluate. It has no leading action verb — the list of payloads does the identifying work instead.

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?

No explicit when-to-use statement or named alternative. The single word 'Free' implicitly signals cost-based selection against paid siblings like evaluate/score, but the agent must infer that comparison rather than being told it.

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