Skip to main content
Glama
Sign In
Vestige

Vestige

by engr-rabbi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Run self-diagnostics

vestige_diagnostics
Read-only

Check Vestige versions, configuration facts, data directories, and provider availability to troubleshoot setup issues without exposing secrets.

Instructions

Report versions, configuration facts, data directories, and provider availability. Never contains secrets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

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=false, so the safety profile is covered. The description adds a genuine trust fact beyond that: the output never contains secrets, which tells an agent the result is safe to surface or forward. It does not mention cost, latency, or whether provider availability probing can be slow.

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?

Two short sentences, zero filler. The inventory of what gets reported comes first, and the secrecy guarantee follows as a compact qualifier.

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?

For a zero-parameter read-only tool with no output schema, the description tells the agent enough to call it unattended: what categories of information come back and that nothing sensitive is included. It could go slightly further by hinting at the shape or size of the response, but nothing essential is missing.

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 per the baseline there is nothing the description needs to disambiguate. The schema is a closed empty object and the description correctly refrains from inventing arguments.

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?

Specific verb ("Report") plus an enumerated set of resources: versions, configuration facts, data directories, provider availability. This clearly separates it from action-oriented siblings like vestige_analyze or vestige_export_report, though it partially overlaps with vestige_list_providers without acknowledging that.

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 implied by the name and content list — an agent would infer this is the pre-flight/troubleshooting call — but the description never says when to reach for it (e.g., before an analyze run, when a job fails) or when vestige_list_providers is the better choice.

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

Deploy Server

Other Tools