Wraith MCP Server

Overview Schema Source Related Servers Discussions Admin

fill_vault_item

Fills a visible web field with a specified vault item field, resolving the item via a registered provider and returning only success or an error, never secret text.

Instructions

Fill a visible field from a vault item.

The registered provider resolves the item inside Wraith. This tool returns only true or an error without secret text. It never returns a snapshot.

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": {
      "index": "<index>",
      "item_id": "<item_id>",
      "field_kind": "<field_kind>"
    },
    "name": "fill_vault_item"
  }
}

Input Schema

Name	Required	Default
`index`	Yes
`item_id`	Yes
`provider`	No	vault
`field_kind`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.6.4Oct 2, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return profile ('only true or an error without secret text') and the negative guarantee ('never returns a snapshot'), but says nothing about permissions, preconditions (field must be visible/focused), or failure modes beyond 'an error'.

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?

Three short sentences, front-loaded with the core action, with no filler. Minor formatting noise (double backticks) but the content is tight and earns its place.

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?

The tool mutates page state with zero annotations and 0% parameter documentation. The description covers output shape (partly redundant with the existing output schema) but leaves parameter meaning, auth needs, and preconditions unexplained, so it is not complete enough for a 4-param write action.

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 4 parameters (index, item_id, provider, field_kind). The description only vaguely gestures at 'provider' and explains none of index, item_id, or field_kind, so it fails to compensate for the undocumented schema.

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+resource ('Fill a visible field from a vault item') and clarifies the item is resolved by the registered provider. It does not explicitly distinguish itself from the close siblings fill_secret or type_text, so an agent must infer the boundary.

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?

No when-to-use guidance and no alternatives named. Given siblings like fill_secret and type_text, the description should say when to prefer this tool over those, but it offers nothing beyond an implied 'fill a field' context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.