Skip to main content
Glama

Vaultan

Facts about the Vaultan app

about_vaultan
Read-onlyIdempotent

What the Vaultan app is, who publishes it, the platforms it is on, where to download it, its price, and where its security design and privacy policy are published.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the full safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description need not restate that. It does add that the content is limited to identity/pricing/security-policy facts, but says nothing about currency, versioning, or that the call is a static lookup with no arguments — modest added value beyond the annotations.

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?

A single sentence with no filler, front-loading the core identity question before the supporting facts. The parallel enumeration is readable, though the trailing 'where its security design and privacy policy are published' clause is slightly denser than the rest.

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 output schema, the description carries the burden of describing return content, and it does so by listing the fact categories covered. It stops short of saying anything about format, staleness, or app version coverage, which keeps it from fully closing the loop for an information-lookup tool.

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 clarify; the baseline of 4 applies. The description correctly implies a parameterless, one-shot informational call.

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 exactly what the tool returns: what Vaultan is, its publisher, platforms, download location, price, and where security/privacy documentation lives. That is a clear resource-level statement of purpose, though it phrases itself as a content list rather than a verb+resource and makes no explicit contrast with the sibling browser tools.

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 can infer this is the tool for answering questions about the Vaultan app itself. There is no explicit statement of when to prefer it over siblings such as find_pages or read_page, and no exclusions or prerequisites.

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.

Resources