Skip to main content
Glama

AANet

by space.aanet
OverviewDiscussionsAdmin

aanet_update_subkey

Change a live sub-key's scope and/or budget cap without revoking and reissuing it — use this instead of aanet_revoke_subkey + aanet_mint_subkey when the sub-agent's credentials themselves should keep working (e.g. widening its file scope mid-task, or raising a budget cap it hit). Owner_key required. Fields left unset are unchanged, not cleared.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesBearer credential for this workspace: either the owner_key returned once by aanet_create_workspace/aanet_create_trial_workspace, or a sub-key returned by aanet_mint_subkey. Sent under the hood as `Authorization: Bearer <api_key>`. Owner-only tools reject a sub-key with a 403.
subkey_idYesThe subkey_id from aanet_mint_subkey or aanet_list_subkeys.
budget_capNoNew spending cap. Leave unset to keep the current value unchanged.
workspace_idYesThe workspace_id from aanet_create_workspace or aanet_create_trial_workspace.
path_scope_prefixNoNew path-scope prefix. Leave unset to keep the current value unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"Bearer credential for this workspace: either the owner_key returned once by aanet_create_workspace/aanet_create_trial_workspace, or a sub-key returned by aanet_mint_subkey. Sent under the hood as `Authorization: Bearer <api_key>`. Owner-only tools reject a sub-key with a 403."
    • changedInput schema / properties / budget_cap / anyOf
      Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / budget_cap / description
      Added value: +"New spending cap. Leave unset to keep the current value unchanged."
    • addedInput schema / properties / path_scope_prefix / description
      Added value: +"New path-scope prefix. Leave unset to keep the current value unchanged."
    • addedInput schema / properties / subkey_id / description
      Added value: +"The subkey_id from aanet_mint_subkey or aanet_list_subkeys."
    • addedInput schema / properties / workspace_id / description
      Added value: +"The workspace_id from aanet_create_workspace or aanet_create_trial_workspace."
  2. First observed

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the critical partial-update semantics ('Fields left unset are unchanged, not cleared') and clarifies that it works 'live' without invalidating credentials. However, it omits details about the response format, error handling, or any side effects (e.g., whether changes are immediately reflected or atomic). While helpful, it does not fully cover the behavioral profile of 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?

Three sentences, each earning its place: the first defines purpose and the key alternative, the second gives concrete motivating examples, the third clarifies partial-update semantics. Critical info (purpose, alternative, partial behavior) is front-loaded, and there is no redundancy or fluff.

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 moderate-complexity mutation tool with no output schema and no annotations, the description covers purpose, usage, and parameter behavior well. However, it does not describe what the tool returns on success or failure, whether there are rate limits, or what happens if the subkey_id is invalid. Given the lack of an output schema, these omissions leave some gaps for an agent to safely invoke the tool.

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

Parameters4/5

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

Schema coverage is 100%, providing solid descriptions for all parameters. The description adds meaningful nuance: it clarifies that unset means 'unchanged' rather than 'cleared', and gives real-world examples for path_scope_prefix (widening file scope) and budget_cap (raising a cap it hit). This goes beyond the schema's generic 'Leave unset to keep the current value' by tying them to concrete use cases, so it compensates well despite the baseline.

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?

The description states a specific verb ('Change') and resource ('live sub-key'), and explicitly distinguishes itself from the revoke-then-mint alternative, giving clear scope. It names exactly what it modifies (scope and/or budget cap) and what it avoids (revoking and reissuing), making it unmistakable even among 24 sibling tools.

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

Usage Guidelines5/5

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

The description explicitly says 'use this instead of aanet_revoke_subkey + aanet_mint_subkey' and gives concrete conditions (when credentials should keep working, e.g., widening scope mid-task or raising a budget cap). It also states the owner_key requirement, leaving no ambiguity about when to call this tool over others.

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

All AANet toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources