Skip to main content
Glama

Cloud Admin Manage Tool

admin_manage

Suspend compromised teams, adjust billing, force-rotate user sessions, and browse cross-team security signals for incident response and platform-wide security review.

Instructions

Platform super-admin operations — suspend tenants, adjust billing, force-rotate user sessions, browse cross-team security signals. Restricted to users with is_super_admin=true (HTTP 403 for all other callers regardless of team role). Every write is audit-logged with the calling super-admin's id, target id, and reason.

When to use: incident response (suspend a compromised team, revoke leaked sessions), customer-success billing adjustments, or platform-wide security review. Do NOT use for routine tenant operations — those have team-scoped tools.

Actions (pass alongside action):

  • team_suspend (DESTRUCTIVE — disables tenant logins) — team_id (UUID), reason (string). Existing API tokens for the team are invalidated; users see a 403 on all API calls.

  • team_billing (read) — team_id. Returns current invoice + plan summary, including next-cycle estimate.

  • billing_credit (write — moves money) — team_id, amount (positive integer cents), reason (string). Adds to the team's CreditLedger; reflects in the next invoice.

  • billing_refund (DESTRUCTIVE — issues a real Stripe refund) — team_id, amount (cents). Refunds against the most recent successful charge; partial refunds supported.

  • security_overview (read) — recent suspicious activity across all teams: failed logins, token leaks, abuse signals.

  • user_revoke_sessions (DESTRUCTIVE) — user_id (UUID). Invalidates ALL sessions and Sanctum/Passport tokens for the user; they must re-authenticate everywhere.

  • user_send_password_reset (write) — user_id. Emails a password-reset link with a 60-minute one-time token.

Cloud note: feedback management (feedback_list/feedback_update) lives under platform support tooling, not exposed via MCP. Errors: 401, 403 (not super-admin), 404, 422, 429, 503 (Stripe down for billing actions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: team_suspend, team_billing, billing_credit, billing_refund, security_overview, user_revoke_sessions, user_send_password_reset
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.
team_idYesUUID of the team to suspend or reactivate
reasonNoReason for suspension (required when suspending)
amount_centsYesAmount in cents (negative to add credit, e.g. -1000 = €10 credit)
descriptionNoDescription for the balance transactionAdmin credit
payment_intent_idYesStripe payment_intent ID to refund (e.g. pi_...)
user_idYesUUID of the user whose tokens to revoke
Behavior5/5

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

No annotations provided, so description carries full burden. It details audit logging, destructive side effects (token invalidation, Stripe refunds, session revocation), and error codes. No contradiction.

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?

Well-structured with sections, but slightly verbose. Front-loaded purpose and actions list. Earns its length but could be trimmed.

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

Completeness3/5

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

No output schema, and description only specifies return for team_billing. Other actions lack output description. Covers actions but misses return values for most, leaving a gap for the agent.

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% but description adds behavioral context for each action beyond schema descriptions (e.g., token invalidation for team_suspend). However, some parameters like description and payment_intent_id are not elaborated.

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 states it's for super-admin operations with specific verbs like suspend, adjust, force-rotate, and browse. It distinguishes from sibling tools by noting that routine tenant operations use team-scoped tools.

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?

Explicitly provides when to use (incident response, billing adjustments, security review) and when not (routine tenant ops). Also mentions restriction to super-admin role with HTTP 403 for others.

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