Skip to main content
Glama

Cloud System Manage Tool

system_manage

Administer and monitor FleetQ MCP server systems by managing KPIs, health checks, security policies, audit logs, cache, and global settings.

Instructions

System administration and monitoring. Actions: dashboard_kpis, health, version_check, audit_log, global_settings, blacklist, security_policy, cache_stats, cache_purge, compute, runpod, browser_relay (relay browser actions to local bridge agent).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: dashboard_kpis, health, version_check, audit_log, global_settings, blacklist, security_policy, cache_stats, cache_purge, compute, runpod, browser_relay
forceNoBypass the cache and fetch the latest version from GitHub immediately.
subject_typeNoFilter by subject type (e.g. experiment, agent, approval)
ocsf_class_uidNoFilter by OCSF class UID (e.g. 3002 = API Activity, 3001 = Account Change, 3006 = Financial Activity, 1001 = Process Activity, 4002 = HTTP Activity)
limitNoMax results to return (default 20, max 100)
settingsYesKey-value pairs to update. Allowed keys: assistant_llm_provider, assistant_llm_model, default_llm_provider, default_llm_model, budget_cap_credits, rate_limit_rpm, outbound_rate_limit, experiment_timeout_seconds, weekly_digest_enabled, audit_retention_days
operationYeslist: get all blacklist entries | add: add a new entry | remove: remove an entry by id
typeNoRequired for add. Type of entry to block.
valueNoRequired for add/remove. The value to block (e.g. "spam@example.com") or the entry UUID to remove.
reasonNoOptional reason for add operations. Stored for audit purposes.
policyNoRequired for update. Policy fields to set.
providerNoFilter by provider (e.g. "anthropic"). Omit to purge all.
modelNoFilter by model (e.g. "claude-sonnet-4-5-20250929"). Omit to purge all.
expired_onlyNoWhen true, only purge entries past their expiry date.
api_keyNoAPI key for credential_save
endpoint_idNoProvider endpoint/model identifier (required for health_check and run)
inputNoInput payload for run
use_syncNoUse synchronous mode for run (default: true)
timeout_secondsNoMax wait time in seconds for run (default: 90)
job_idNoJob ID returned by endpoint_run async mode (required for endpoint_status)
pod_idNoPod ID for pod_status or pod_stop
pod_configNoPod configuration for pod_create (imageName, gpuTypeIds, gpuCount, env, etc.)
toolNoBrowserMCP tool name (required for call_tool)
paramsNoTool parameters for BrowserMCP (optional for call_tool)
Behavior2/5

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

Annotations are empty, so description carries full burden. Fails to disclose that cache_purge is destructive, that compute/runpod actions consume budget/resources, or that browser_relay requires a local bridge. No mention of rate limits, async job handling, or side effects.

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

Conciseness3/5

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

Single sentence is compact and front-loaded with the category, but wastes space listing 11 enum strings verbatim that are already in the schema. Could have used that space to explain parameter relationships or action categories.

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?

Severely inadequate for a 24-parameter kitchen-sink tool spanning monitoring, security, compute, and browser automation. No explanation of which parameters apply to which actions (e.g., 'subject_type' only for audit_log, 'pod_config' only for runpod), forcing the agent to guess parameter relevance.

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 has 100% description coverage, establishing baseline 3. Description adds minimal value beyond schema—the parenthetical for browser_relay is helpful, but other actions get no semantic clarification. The schema incorrectly marks 'settings' and 'operation' as universally required, which description doesn't correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States 'System administration and monitoring' which categories the tool, but primarily duplicates the action enum list already present in the schema. Doesn't differentiate from sibling 'admin_manage' or clarify the scope boundaries of this tool versus others.

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?

Provides no guidance on when to select this tool over siblings, no prerequisites for specific actions (e.g., when cache_purge vs cache_stats is appropriate), and no warning about destructive operations like purge or blacklist modifications.

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