Skip to main content
Glama

update_agent_profile

DestructiveIdempotent

Updates only the calling agent's own profile fields—role, capabilities, responsibility zone, working hours, and related settings—while omitted fields stay unchanged and other agents cannot be edited.

Instructions

Update the calling agent's own profile fields such as role, capabilities, responsibility zone, and working hours. Only the fields you pass are sent; omitted ones keep their values. It cannot edit another agent.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_agent_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoAgent role (e.g. developer, reviewer, tester).
modelNoModel this agent runs on (max 128 chars). Empty string clears it.
agent_typeNoHarness this agent runs in: claude_code, codex, cursor, copilot, gemini_cli, openclaw, cline, aider, hermes, custom.
descriptionNoHuman-readable description of the agent's purpose.
accepts_fromNoAgent IDs or types this agent accepts tasks from.
callback_urlNoURL where Mesh will POST task events (task.assigned, task.status_changed, task.commented). Set to empty string to disable.
capabilitiesNoList of capability strings (e.g. go, react, testing).
escalation_toNoAgent ID or name to escalate issues to.
working_hoursNoWorking hours description (e.g. 24/7, 9-17 UTC).
responsibility_zoneNoArea of responsibility (e.g. Backend, Frontend).
max_concurrent_tasksNoMaximum number of tasks this agent works on at once, a positive integer. Shown in the team directory for whoever assigns work. Omit to leave it unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / max_concurrent_tasks / description
      Previous value: -"Maximum number of concurrent tasks this agent can handle."New value: +"Maximum number of tasks this agent works on at once, a positive integer. Shown in the team directory for whoever assigns work. Omit to leave it unchanged."
  2. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, and readOnly=false, so the agent knows the safety profile. The description adds useful behavioral context beyond annotations: partial-update semantics and the self-only restriction. It does not explain auth requirements or side effects in depth, but the added context is meaningful.

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 short sentences, front-loaded with the action and scope, then the partial-update rule, then the boundary condition. No wasted wording.

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?

For an 11-parameter mutation tool with no output schema, the description covers the essential call semantics: self-only scope and partial updates. Annotations cover the destructive/idempotent profile, though return behavior and auth requirements are not described, leaving a minor gap.

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 coverage is 100%, so all 11 parameters are already documented in the input schema. The description adds the partial-update principle and names a few example fields, but does not add per-parameter meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 and resource, 'Update the calling agent's own profile fields,' and adds the self-only scope with 'It cannot edit another agent.' This makes it clearly distinguishable from agent-registration or team-directory siblings.

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?

Explains the key usage condition that only passed fields are sent while omitted fields retain their values, and explicitly excludes editing another agent. It does not name alternative tools, but the context is clear enough for correct selection.

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