Skip to main content
Glama

update_agent

Idempotent

FULL-REPLACE update of an agent's draft (send every field to keep — this is PUT, not PATCH). Does not change the live published revision; publish_agent does.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>",
      "name": "<name>",
      "base_prompt": "<base_prompt>",
      "model": "<model>"
    },
    "name": "update_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesagent display name
modelYesmodel id from the workspace's model catalog (GET /v1/models)
voiceNoTTS voice id
accentNospeaking accent hint
purposeNoRequired on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
agent_idYesagent UUID
base_promptYessystem prompt defining persona and rules
speech_styleNospeaking style hint
max_call_minutesNohard per-call duration cap

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds valuable behavioral context by disclosing that the change is a 'FULL-REPLACE' operation—meaning every field is sent and overwritten—a detail critical for understanding the mutation pattern.

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?

The definition is extremely concise and highly efficient; both sentences deliver maximum functional and technical context without any unnecessary filler.

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?

The description successfully covers the two most critical operational aspects: the 'full-replace' methodology and the distinction between draft and live revisions. This makes it complete for a complex update operation.

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?

With 100% schema description coverage, the description does not need to add semantic value to individual parameters. It adheres to the baseline score when the schema is perfectly documented.

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 clearly identifies the action ('FULL-REPLACE update') and the target (an agent's draft), specifying the technical method (PUT vs PATCH) which is highly specific.

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?

It provides explicit usage guidance by stating that the tool only affects the draft and explicitly refers to the `publish_agent` sibling tool as the required action for live publication.

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