Skip to main content
Glama
dnotitia

akb

by dnotitia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

akb_transfer_ownership

Transfer vault ownership to a new user. Current owners or admins can reassign vaults to another username.

Instructions

Transfer vault ownership to another user. The current owner or a system admin can do this.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vaultYesVault name
new_ownerYesUsername of the new owner
_vault_skill_ackNoOpaque acknowledgement returned as vault_skill.ack_token. After applying that guide, retry the unchanged operation with this value. The bundled proxy supplies it automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.14
    • addedInput schema / properties / _vault_skill_ack
      Added value: +{
+  "description": "Opaque acknowledgement returned as vault_skill.ack_token. After applying that guide, retry the unchanged operation with this value. The bundled proxy supplies it automatically.",
+  "maxLength": 128,
+  "type": "string"
+}
  2. Addedv2.0.4
  3. Removedv2.0.1
  4. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does add one meaningful behavioral fact — the permission requirement (current owner or system admin). However, it does not disclose what happens to the previous owner after transfer, whether the new owner must already be a vault member, or whether the operation is reversible, all of which are material for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences totaling roughly 15 words with the core action front-loaded ('Transfer vault ownership to another user') and the authorization note in a short second sentence. Zero filler; every word earns its place.

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 simple two-required-parameter mutation with no output schema and no annotations, the description covers the basic what and who. But it omits the post-transfer state of the previous owner, any prerequisites for the new owner, and the return value — gaps an agent would need to resolve before confidently invoking the tool.

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 100% (vault = 'Vault name', new_owner = 'Username of the new owner'), so the baseline is 3. The description adds no extra parameter detail beyond what the schema already provides, such as format, lookup behavior, or constraints on the username.

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

Purpose5/5

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

Description states a specific verb (Transfer), resource (vault ownership), and destination (another user) in a single crisp sentence. This clearly distinguishes the tool from access-management siblings like akb_grant, akb_revoke, and akb_vault_members, which operate on permissions rather than ownership.

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?

The description conveys the authorization context ('The current owner or a system admin can do this'), which tells the agent when the call is permitted. However, it offers no explicit guidance on when to prefer this over related siblings such as akb_grant or akb_vault_members, nor does it state when not to use it.

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