Skip to main content
Glama
escapeboy

FleetQ

by escapeboy
OverviewSchemaRelated ServersScoreDiscussions
Hybrid

Agent Advanced Tool

agent_advanced
Destructive

Inspect agent configuration history, rollback to past versions, check live runtime state, sync skills or tools, and submit or review user feedback.

Instructions

Auxiliary agent operations beyond core CRUD: configuration history, rollback, live runtime inspection, skill/tool wiring, user feedback. For create/update/delete/toggle use agent_manage. Every action requires agent_id; remaining params depend on action.

Actions:

  • config_history (read) — agent_id. Past config snapshots with timestamps.

  • rollback (DESTRUCTIVE) — agent_id, version. Overwrites the current config with the named snapshot — current state is lost unless already snapshotted.

  • runtime_state (read) — agent_id. Last execution status, queue depth, error counters.

  • skill_sync (write) — agent_id, skill_ids[]. Replaces attached skills (full set semantics).

  • tool_sync (write) — agent_id, tool_ids[]. Replaces attached tools (full set semantics).

  • feedback_submit (write) — agent_id, rating (1-5), comment.

  • feedback_list (read) — agent_id. Recent feedback entries.

  • feedback_stats (read) — agent_id. Aggregate score + sentiment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: config_history, rollback, runtime_state, skill_sync, tool_sync, feedback_submit, feedback_list, feedback_stats
deadline_msNoOptional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
agent_idYesThe agent UUID
limitNoMax revisions to return (default 20, max 50)
revision_idYesThe revision UUID to roll back to (restores the before_config of that revision)
skill_idsYesArray of skill UUIDs to attach/detach/sync
modeNoOperation mode: sync (replace all), attach (add), detach (remove). Default: sync
tool_idsYesArray of tool UUIDs to attach/detach/sync
execution_idYesThe AgentExecution UUID to rate
scoreYes1 = positive, -1 = negative, 0 = neutral
commentNoOptional comment explaining the rating
correctionNoOptional correct output (for negative feedback)
labelNoOptional failure category label
daysNoLookback period in days (default 30)

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

Annotations already provide destructiveHint: true, but the description adds significant context: 'rollback (DESTRUCTIVE) — ... current state is lost unless already snapshotted.' It also marks other actions as read/write. This goes well beyond the annotation.

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 description is well-structured with bullet points for each action, front-loaded with an overall summary. Every sentence is informative and necessary, with no extraneous 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?

Despite having no output schema, the description hints at return values for each action (e.g., 'Past config snapshots with timestamps,' 'Last execution status, queue depth, error counters'). It covers all actions adequately for an agent to select and use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining action-dependent parameters: 'Every action requires agent_id; remaining params depend on action.' It also elaborates on parameters like mode for skill_sync/tool_sync, which is not obvious from the schema alone.

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 starts with a clear summary: 'Auxiliary agent operations beyond core CRUD.' It explicitly lists all actions and distinguishes from the sibling 'agent_manage' tool by stating 'For create/update/delete/toggle use agent_manage.' This provides unambiguous differentiation.

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?

The description explicitly tells when to use this tool vs. alternatives: 'For create/update/delete/toggle use agent_manage.' It also categorizes each action with (read), (DESTRUCTIVE), or (write), guiding appropriate usage. No additional exclusions needed.

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