Skip to main content
Glama

Use a granular connected-service capability

vault_execute
Destructive

Execute one reviewed granular capability as the connected user, including approval-gated actions.

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": {
      "account_id": "<account_id>",
      "capability_id": "<capability_id>"
    },
    "name": "vault_execute"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
account_idYes
approval_idNo
capability_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, so the risk profile is known from structured data. The description adds two pieces of real context not in the annotations: execution happens 'as the connected user' (identity/auth context) and some actions are 'approval-gated' (implying an approval handshake). It still says nothing about irreversibility, rate limits, or what a rejected approval looks like.

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 front-loaded sentence with no filler or redundancy. It is efficiently written, though its brevity is under-specification rather than true concision given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world, non-idempotent executor with a nested free-form params object, no output schema, and zero schema coverage, one sentence is far from enough. An agent cannot tell what a capability_id looks like, how to populate params, or when approval_id is mandatory.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, including a free-form nested 'params' object, so the description carries the full burden and mostly fails it. The only semantic hint is 'approval-gated actions', which weakly gestures at approval_id; account_id, capability_id, and especially the shape of params are entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb ('Execute') and a scoped object ('one reviewed granular capability as the connected user'), so the basic operation is discernible. However, 'granular capability' is never explained, and the description gives no basis for choosing this tool over siblings such as vault_invoke_read or vault_invoke_write, which plausibly do overlapping work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no named alternative, despite a sibling set containing vault_invoke_read, vault_invoke_write, and vault_autonomy that an agent would need to disambiguate. 'Reviewed' and 'approval-gated' hint at a governance workflow but never state the conditions under which this tool is the correct choice.

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