Aident AI

Manage Aident Vault connections

vault

Destructive

Manage Loadout Vault connections: check status, connect, or disconnect integrations.

Input Schema

Name	Required	Description	Default
`action`	No		status
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`confirmed`	No	Deprecated compatibility field
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`addAccount`	No	Connect only: add a new account instead of reconnecting the default account (--addAccount).
`credentials`	No	Plaintext credential values for programmatic callers. Agent callers should omit this field and send the returned connectUrl to the user instead of asking for secrets in chat.
`accountAlias`	No	Account alias selector: on connect, reconnect exactly that account (requires replaceAccountConfirmed); on disconnect, delete exactly that account (--accountAlias).
`integrationId`	No	Integration ID to check, connect, or disconnect
`integrationIds`	No	Integration IDs to check
`capabilityNames`	No	Capability names whose integration dependencies to check
`redirectAfterConnect`	No	Relative URL to visit after OAuth connection completes
`replaceAccountConfirmed`	No	Caller-asserted acknowledgement that reconnecting may replace the provider identity behind the selected account alias (--replaceAccountConfirmed).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

addedInput schema / required

Added value: +[
+  "context",
+  "llm_model"
+]

Changed3 schema fields changedAug 14, 2026

addedInput schema / properties / accountAlias

Added value: +{
+  "description": "Account alias selector: on connect, reconnect exactly that account (requires replaceAccountConfirmed); on disconnect, delete exactly that account (--accountAlias).",
+  "type": "string"
+}

addedInput schema / properties / addAccount

Added value: +{
+  "description": "Connect only: add a new account instead of reconnecting the default account (--addAccount).",
+  "type": "boolean"
+}

addedInput schema / properties / replaceAccountConfirmed

Added value: +{
+  "description": "Caller-asserted acknowledgement that reconnecting may replace the provider identity behind the selected account alias (--replaceAccountConfirmed).",
+  "type": "boolean"
+}

First observedAug 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description does not say which action is destructive (disconnect deletes an account per the schema), that connect may return a URL rather than completing inline, or that account replacement requires confirmation. For a destructive three-action tool it adds essentially no behavioral context.

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 tight sentence with the resource front-loaded and the action list following. No waste, though brevity comes at the cost of substance for a 12-parameter tool.

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?

With 12 parameters, nested objects, no output schema, and destructive behavior, one sentence is not enough. It omits which parameters apply to which action, the credentials-vs-connectUrl flow, and what any action returns.

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 description coverage is 92%, so parameters are well documented in the schema itself. The description adds nothing about parameter semantics or action-dependent parameter applicability, which is the only meaningful gap it could have filled.

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?

The description names a specific resource ('Loadout Vault connections') and enumerates the three supported verbs (status, connect, disconnect), matching the action enum. It is clear what the tool does, though it offers no differentiation from similarly named siblings such as auth or capabilities.

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?

It lists the three actions but gives no guidance on when to use which one, no prerequisites, and no alternatives to consider. An agent must infer that 'status' is the default and that 'connect' may involve an OAuth round-trip purely from the schema.

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

All Aident AI tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?