Skip to main content
Glama

Update draft agent

update_agent

Update a draft's fields (model, tools, system message, knowledge...). status/workflow/organization/user are refused with reasons.

Input Schema

NameRequiredDescriptionDefault
fieldsYesPartial map of fields to change (send only what changes). Accepted: name, avatar, description, model_id, model_provider, model_config, reasoning_config, hitl_config, system_message, tags, metadata, needed_tools, needed_agents, memory_config, pattern_type, pattern_config, capabilities, is_memory_enabled, use_byok, byok_fallback_to_system, enable_rich_content, rich_content_types, rich_content_prompt_mode, enable_file_tools, enable_python_repl, enable_artifacts, vector_stores, files, is_public. `metadata` and `pattern_config` merge key-wise (send a key to replace it, null to delete). status/workflow/organization and relation fields (mcp_servers, api_endpoints, ai_tools, governance_policies, used_triggers) are refused here — use the dedicated attach_*/set_* tools instead. Number-only settings (model_config temperature/top_p/max_tokens, pattern_config max_steps/recursion_limit, workflow node retry/node_timeout_sec/timeout_sec, ...) must be numbers within range; a clean numeric string is accepted, anything else (text, true/false) is refused with the field named and nothing is saved.
agent_idYesId of the draft agent to update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / description
      Previous value: -"Partial map of fields to change (send only what changes). Accepted: name, avatar, description, model_id, model_provider, model_config, reasoning_config, hitl_config, system_message, tags, metadata, needed_tools, needed_agents, memory_config, pattern_type, pattern_config, capabilities, is_memory_enabled, use_byok, byok_fallback_to_system, enable_rich_content, rich_content_types, rich_content_prompt_mode, enable_file_tools, enable_python_repl, enable_artifacts, vector_stores, files, is_public. `metadata` and `pattern_config` merge key-wise (send a key to replace it, null to delete). status/workflow/organization and relation fields (mcp_servers, api_endpoints, ai_tools, governance_policies, used_triggers) are refused here — use the dedicated attach_*/set_* tools instead."New value: +"Partial map of fields to change (send only what changes). Accepted: name, avatar, description, model_id, model_provider, model_config, reasoning_config, hitl_config, system_message, tags, metadata, needed_tools, needed_agents, memory_config, pattern_type, pattern_config, capabilities, is_memory_enabled, use_byok, byok_fallback_to_system, enable_rich_content, rich_content_types, rich_content_prompt_mode, enable_file_tools, enable_python_repl, enable_artifacts, vector_stores, files, is_public. `metadata` and `pattern_config` merge key-wise (send a key to replace it, null to delete). status/workflow/organization and relation fields (mcp_servers, api_endpoints, ai_tools, governance_policies, used_triggers) are refused here — use the dedicated attach_*/set_* tools instead. Number-only settings (model_config temperature/top_p/max_tokens, pattern_config max_steps/recursion_limit, workflow node retry/node_timeout_sec/timeout_sec, ...) must be numbers within range; a clean numeric string is accepted, anything else (text, true/false) is refused with the field named and nothing is saved."
  2. Changed2 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Id of the draft agent to update."
    • addedInput schema / properties / fields / description
      Added value: +"Partial map of fields to change (send only what changes). Accepted: name, avatar, description, model_id, model_provider, model_config, reasoning_config, hitl_config, system_message, tags, metadata, needed_tools, needed_agents, memory_config, pattern_type, pattern_config, capabilities, is_memory_enabled, use_byok, byok_fallback_to_system, enable_rich_content, rich_content_types, rich_content_prompt_mode, enable_file_tools, enable_python_repl, enable_artifacts, vector_stores, files, is_public. `metadata` and `pattern_config` merge key-wise (send a key to replace it, null to delete). status/workflow/organization and relation fields (mcp_servers, api_endpoints, ai_tools, governance_policies, used_triggers) are refused here — use the dedicated attach_*/set_* tools instead."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare it is not read-only, not destructive, and closed-world. The description adds useful behavioral context by stating that certain fields are refused with reasons and that the target is a draft agent.

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 tightly written sentences with the core purpose and refusal boundary front-loaded. There is no redundant or wasted text.

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?

Given the rich schema and annotations, the description covers what the tool is for and which fields are refused. It does not describe return or error behavior, but the most important invocation details are already 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%, so the schema already fully documents agent_id and the nested fields map, including accepted fields, merge behavior, and numeric validation. The description only adds examples and repeats a few refusals, which is baseline-level added meaning.

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?

States a specific verb ('Update') and resource ('draft's fields'), with examples and an explicit boundary for refused fields such as status/workflow/organization/user. This clearly distinguishes it from create/archive/attach 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 Guidelines4/5

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

Gives clear context that this is for updating draft-agent fields and names fields that are refused. However, the description itself does not route the agent to the dedicated attach_*/set_* alternatives, even though the schema does.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources