Skip to main content
Glama
Sign In
vaultre-mcp

vaultre-mcp

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

vaultre_click

Clicks a numbered element on the current VaultRE page to navigate or trigger actions, using the element number from the last page read.

Instructions

Click a numbered element on the current VaultRE page.

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": {
      "element": "<element>"
    },
    "name": "vaultre_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It states that a click happens but not what the click does (navigation, form submission, modal), whether it waits for the page to settle, or what happens when the element number is stale or invalid.

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?

One sentence with no wasted words and the action front-loaded. Its brevity is efficient, though it edges toward under-specification rather than maximal clarity.

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?

For a one-parameter browser-automation tool with no output schema, the definition omits post-click behavior and error handling, which an agent needs in order to chain actions reliably. The page-scoping phrase ("current page") is the only added context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented as an element number sourced from the last read. The description adds nothing beyond the schema, so the baseline 3 applies.

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?

Names a specific verb and target: "Click a numbered element on the current VaultRE page." Combined with the sibling set (read, type, open, close, status), an agent can infer this is the element-level interaction tool, though the description itself does not explicitly contrast with vaultre_type or vaultre_read.

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?

Use is only implied: the schema note "Element number from the last read" suggests this must follow vaultre_read, but the description never states that prerequisite, nor when to prefer clicking over typing or opening a URL.

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