Skip to main content
Glama

Agent Manage Tool

agent_manage

Manage AI agents in FleetQ by creating, updating, deleting, and monitoring their status, roles, and configurations for automated workflows.

Instructions

Manage AI agents. Actions: list (filter by status, limit), get (agent_id), create (name, role, goal, provider, model), update (agent_id + fields), delete (agent_id, confirm=true), toggle_status (agent_id), templates (list agent templates).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: list, get, create, update, delete, toggle_status, templates
statusNoFilter by status: active, disabled
limitNoMax results to return (default 10, max 100)
agent_idYesThe agent UUID
nameYesAgent name
roleNoAgent role description
goalNoAgent goal
backstoryNoAgent backstory
providerNoLLM provider: anthropic, openai, google (default: anthropic)anthropic
modelNoLLM model name (default: claude-sonnet-4-5)
personalityNoAgent personality traits: {tone, communication_style, traits[], behavioral_rules[], response_format_preference}
data_classificationNoData classification level: public, internal, confidential, restricted. Confidential and restricted agents are routed to local-only providers.
sandbox_profileNoJSON string defining Docker sandbox profile for per-execution process isolation (enterprise only). Example: {"image":"python:3.12-alpine","memory":"512m","cpus":"1.0","network":"none","timeout":300}
budget_cap_creditsNoPer-agent budget cap in credits. Set to 0 to remove cap.
confirmYesMust be true to confirm deletion. This is a destructive action.
categoryNoFilter by category: engineering, content, business, design, research
Behavior2/5

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

With empty annotations, the description carries the full burden of behavioral disclosure but offers minimal insight. It mentions 'confirm=true' for deletion but doesn't clarify if deletions are permanent, what toggle_status does (enable/disable?), or how the sandbox_profile isolation behaves. Missing disclosure of side effects for data_classification routing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single dense sentence efficiently packs action-parameter mappings. No redundant fluff, though the parenthetical format creates slight readability friction. Front-loaded with primary verb and resource.

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

Completeness2/5

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

Complex multi-action tool with 16 parameters, nested objects, and no output schema or annotations. The description under-explains behavioral complexity (e.g., budget_cap_credits interaction, template structure, destructive confirmation requirements) given the lack of structured metadata.

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%, establishing baseline 3. The description adds value by mapping actions to their relevant parameters (e.g., 'list (filter by status, limit)'), but doesn't explain complex nested objects like 'personality' or 'sandbox_profile' beyond the schema text.

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?

The description states 'Manage AI agents' with a clear list of actions (list, get, create, update, delete, toggle_status, templates) and associated parameters. However, it fails to distinguish from siblings like 'agent_advanced' or 'admin_manage', leaving ambiguity about which management tool to select.

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

Usage Guidelines2/5

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

While the description lists available actions, it provides no guidance on when to use this tool versus alternatives like 'agent_advanced' or 'crew_manage'. No mention of prerequisites (e.g., needing existing agents for update/delete) or workflow sequences.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/escapeboy/agent-fleet-o'

If you have feedback or need assistance with the MCP directory API, please join our Discord server