Skip to main content
Glama

Vaultan

Find pages on vaultan.app

find_pages
Read-onlyIdempotent

Searches the titles and descriptions of the English pages of vaultan.app (features, browser tools, comparisons, guides, research, security) and returns the best matches with their addresses.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWords to look for, for example "redact pdf" or "photo location".

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, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral detail beyond them: matching is limited to titles and descriptions rather than page bodies, the corpus is English-only, and results come back as matches plus their addresses.

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?

One sentence, front-loaded with the verb and the searched fields, followed by scope and return shape. The parenthetical category list is compact and conveys corpus boundaries rather than padding; nothing here is redundant with 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?

For a simple read-only single-parameter search with no output schema, the definition covers what is searched, the language restriction, and the shape of the return value. Minor gaps remain — no hint about result limits, ranking, or whether a zero-match response is possible — but nothing essential to correct invocation 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?

With a single parameter at 100% schema coverage (including a worked example, "redact pdf"), the baseline is already 3. The description earns the extra point by clarifying what the query is matched against — page titles and descriptions, not full text — which tells the agent how to shape keywords.

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 verb (Searches) and a precisely bounded resource: the titles and descriptions of English pages on vaultan.app, with the topical scope enumerated and the return shape noted ('best matches with their addresses'). This implicitly separates it from read_page (full content) and list_browser_tools (catalog), but it never names or contrasts a sibling explicitly, keeping it just short of a 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 can infer this is the keyword-lookup entry point for the site, but there is no statement of when to prefer it over read_page or list_browser_tools, and no guidance on query phrasing beyond the schema example. No exclusions or prerequisites are given.

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