Skip to main content
Glama

Cloud Team Manage Tool

team_manage

Manage team configurations, members, and security settings in FleetQ. Configure local LLMs, API tokens, notifications, join requests, and encryption keys for team collaboration and control.

Instructions

Manage team settings and members. Actions: get, update, members, local_llm, byok_credential, custom_endpoint (plan-enforced), api_token, notification, join_request (manage team join requests), kms (manage KMS encryption keys).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: get, update, members, local_llm, byok_credential, custom_endpoint, api_token, notification, join_request, kms
nameNoNew team name
settingsNoTeam settings object (merged with existing settings)
providerNoProvider: ollama | openai_compatible (required for configure/remove/discover)
base_urlNoBase URL of the endpoint (e.g. http://localhost:11434)
api_keyNoOptional API key for authenticated endpoints
modelsNoComma-separated model IDs for openai_compatible endpoints
token_idNoToken ID to revoke (required for revoke action)
notification_idNoRequired for mark_read. The notification UUID to mark as read.
titleNoRequired for send. Notification title.
bodyNoRequired for send. Notification body text.
typeNoFor send. Notification type (e.g. agent_alert, budget_warning, info).
action_urlNoFor send. Optional URL the user can click to navigate.
user_idNoFor send. Target user ID. If omitted, notifies all team members.
preferencesNoFor update_preferences. Map of notification_type => array of channels (in_app, mail, push). E.g. {"experiment.stuck": ["in_app","mail","push"]}
request_idNoJoin request UUID (required for approve/deny)
credentialsNoProvider-specific credentials. Required for test and enable. AWS: {role_arn, key_arn, region}. GCP: {project_id, location, key_ring, key_id, service_account_json}. Azure: {tenant_id, client_id, client_secret, vault_url, key_name, key_version?}.
key_identifierNoThe key identifier (ARN for AWS, resource name for GCP, vault URL + key name for Azure). Required for enable.
forceNoForce removal even if KMS is unreachable. Only for remove action.
Behavior3/5

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

Adds minimal behavioral context beyond the empty annotations: notes 'plan-enforced' constraint for custom_endpoint and expands acronyms (KMS). However, fails to clarify mutability (which actions are destructive vs. read-only), side effects, or error handling for the 19-parameter tool.

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 front-loaded but action list largely duplicates the schema enum. The structure is flat (just a list) rather than grouping related actions or indicating parameter relationships, reducing usefulness.

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?

Inadequate for a 19-parameter tool with complex conditional requirements (e.g., provider-specific fields for KMS, notification send requirements). No output schema exists, yet description fails to explain action-specific workflows, return values, or how the nested settings objects behave.

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 redundantly lists the action enum values but adds minimal semantic depth beyond what the schema already documents (e.g., doesn't clarify which parameters are conditionally required for specific actions).

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?

States clear verb+resource ('Manage team settings and members') and enumerates specific supported actions (get, update, members, etc.), though it could better differentiate from sibling management tools like admin_manage or profile_manage.

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 use this tool versus alternatives (e.g., admin_manage), no mention of prerequisites, and no sequencing advice for the complex multi-action workflow.

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