TeamShared

agent_update

Change an agent record: tools, status, standing procedure, lens, focus or spend cap. Needs org:admin; agent seats are refused, and the manager's record is fixed (no cap on the manager).

Input Schema

Name	Required	Description
`slug`	Yes	Agent record slug (agent-<label> or <label>)
`agent`	No	Override agent attribution label
`focus`	No	Strategic focus binding; {} clears
`model`	No	New model pin; empty string clears it (default)
`status`	No	active, paused (starts no runs) or archived
`budget_usd`	No	New spend cap in USD. Omit to leave it. "0" blocks every new run. Set with budget_period when the agent has no cap yet.
`namespaces`	No	Memory lens containers; [] clears
`persona_md`	No	Private standing brief; empty string clears
`mcp_servers`	No	Replace the agent's external MCP servers (#1264); [] clears. Objects with name, url (https), optional tools (allowlist), secret (vault secret name, never a token) and enabled. Offered only when the run's tool allowlist grants them (all, mcp, or ext_<name>__*)
`skill_slugs`	No	Standing skills; [] clears
`clear_budget`	No	Remove the spend cap. Do not also pass budget_usd or budget_period.
`display_name`	No	New display name
`github_grant`	No	Replace the agent's GitHub grant (#1379): {repos: [owner/repo, ...], read, write, destructive}, each level off, auto or ask. To revoke, set the levels to off. Only a person can set it
`budget_period`	No	day, week (Monday) or month, UTC. Omit to leave it.
`tool_patterns`	No	New tool patterns; [] clears them (deployment default)
`playbook_slugs`	No	Standing playbooks; [] clears
`clear_github_grant`	No	Remove the GitHub grant so the agent follows the org default again. Do not also pass github_grant.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

addedInput schema / properties / clear_github_grant

Added value: +{
+  "default": false,
+  "description": "Remove the GitHub grant so the agent follows the org default again. Do not also pass github_grant.",
+  "type": "boolean"
+}

addedInput schema / properties / github_grant

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Replace the agent's GitHub grant (#1379): {repos: [owner/repo, ...], read, write, destructive}, each level off, auto or ask. To revoke, set the levels to off. Only a person can set it"
+}

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / mcp_servers

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Replace the agent's external MCP servers (#1264); [] clears. Objects with name, url (https), optional tools (allowlist), secret (vault secret name, never a token) and enabled. Offered only when the run's tool allowlist grants them (all, mcp, or ext_<name>__*)"
+}

Changed3 schema fields changedOct 20, 2026

addedInput schema / properties / budget_period

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "day",
+        "week",
+        "month"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "day, week (Monday) or month, UTC. Omit to leave it."
+}

addedInput schema / properties / budget_usd

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "New spend cap in USD. Omit to leave it. \"0\" blocks every new run. Set with budget_period when the agent has no cap yet."
+}

addedInput schema / properties / clear_budget

Added value: +{
+  "default": false,
+  "description": "Remove the spend cap. Do not also pass budget_usd or budget_period.",
+  "type": "boolean"
+}

AddedOct 19, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the authorization requirement, two hard refusal cases, and the manager-record exception. It does not say whether unspecified fields are preserved or that list-valued fields are wholesale replacements, but those semantics are stated in the schema rather than contradicted here.

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, zero filler: the first front-loads what changes, the second front-loads the constraints that decide whether the call is even legal. Nothing is repeated from the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the schema covers all 17 params in detail. The description adds the operational gate (org:admin, seat/manager refusals) that an agent cannot infer from the schema; the only gap is that replace-vs-merge semantics live solely in the schema.

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% across 17 parameters, so the schema already explains clearing behavior ('[] clears', 'empty string clears'), the budget/clear_budget interaction, and the MCP/GitHub grant shapes. The description only restates the field families in prose ('tools, status, standing procedure, lens, focus or spend cap') without adding format or interaction detail, so baseline 3 applies.

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 ('Change') plus the resource ('an agent record') and enumerates the mutable surfaces (tools, status, standing procedure, lens, focus, spend cap). It is clearly distinguishable from agent_create/agent_get/agent_list by the mutation verb, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Gives real preconditions and exclusions: 'Needs org:admin; agent seats are refused, and the manager's record is fixed (no cap on the manager).' That tells the agent when the call will fail, but it does not route between this tool and alternatives such as agent_create or the memory_* / agent_routine_set tools that also touch agent configuration.

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

All TeamShared tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.