Skip to main content
Glama

Read browser action result

vault_browser_result
Read-only

Read or consume the result of a previously queued API Vault browser job.

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": {
      "job_id": "<job_id>"
    },
    "name": "vault_browser_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, non-destructive, non-idempotent), so the description's main added signal is the word 'consume', hinting the result may be single-use or drained. That is genuinely useful but left ambiguous, and it sits in mild tension with readOnlyHint=true; nothing is said about pending/failed jobs or expiry.

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, front-loaded with the verb and resource, with no filler. It is arguably too terse for the gaps it leaves, but nothing is wasted.

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?

With no output schema, the description is the only place a reader learns what a 'result' looks like, yet it says nothing about shape, status, or failure modes. For a retrieval tool whose entire value is the returned payload, this leaves a meaningful hole.

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?

The single job_id parameter has 0% schema description coverage, so the description must carry the load. 'Previously queued ... browser job' does establish that job_id is the identifier returned by the queueing call, which is real added meaning, but nothing covers format, validity, or reuse.

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 ('Read or consume') and a specific resource ('result of a previously queued API Vault browser job'). The phrase 'previously queued' implicitly separates it from vault_browser_action, which presumably creates the job, though the sibling is never named.

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: the tool is meant to follow a queued browser job, so the agent can infer it is a post-submission retrieval step. There is no explicit guidance on what to do if the job is still running, whether to poll, or what alternative to use instead of this one.

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