anthropic-admin-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.1
Disambiguation5/5
Each tool has a distinct purpose targeting specific resources (workspaces, members, invites, API keys, usage). No two tools overlap in functionality; even the two report tools (get_cost_report and get_usage_report) clearly separate dollar costs from token usage. The tool set is well-organized with clear boundaries.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (e.g., create_workspace, list_members, update_api_key). Verbs are chosen predictably and match the action being performed. No mixing of conventions like camelCase or inconsistent verb styles.
Tool Count5/5
21 tools is reasonable for the complexity of Anthropic administration, covering organization, workspaces, members, invites, API keys, and usage reports. Each tool addresses a necessary operation without obvious redundancy or bloat.
Completeness3/5
The tool set covers most core admin operations but has notable gaps: no tool to create or delete API keys (only rename/deactivate), and no tool to delete a workspace (only archive). These missing lifecycle operations may cause agents to hit dead ends.
Average 4/5 across 21 of 21 tools scored. Lowest: 3.1/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses a key behavioral fact: actual key values are never returned and cannot be retrieved after creation. This is valuable. However, it does not mention other potential behaviors like pagination or authentication needs.
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?
The description is concise with two short paragraphs. The first sentence is clear, and the second provides useful return field details. No extraneous text.
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?
Given the six parameters and low schema coverage, the description is incomplete. It lacks information on pagination, ordering, and how filters interact. The security disclosure is helpful but insufficient for full understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is low (33%), and the description does not add meaning to the parameters. It only describes the return fields, not how to use the parameters like limit, status, or workspace_id.
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 clearly states the tool lists API keys in the organization, which is a specific verb and resource. However, it does not differentiate from siblings like update_api_key or other list tools, which would be helpful.
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?
No guidance is provided on when to use this tool versus alternatives. The description lacks any recommendations or scenarios for when it is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description mentions expiration and fields but omits rate limits, auth requirements, or pagination behavior beyond schema.
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?
Two sentences, first is clear and direct; second adds useful context but could be more concise.
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?
Provides basic purpose and structure but lacks parameter context and behavioral details for a list tool with pagination.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage 0% and description does not explain parameters (limit, before_id, after_id) despite 3 parameters being present.
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?
Clear verb 'list' and resource 'organization invites', scope 'pending and historical' distinguishes it from invite_member (create) and delete_invite (delete).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for listing invites but no explicit when-to-use vs. alternatives, no exclusions or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. It describes the operation as a read (list) and details pagination, but does not disclose required permissions, rate limits, or whether the list is scoped to the authenticated user's organization. Key behavioral traits are missing.
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?
The description is relatively concise at five lines, with front-loaded purpose. Each sentence (scope, pagination, returned fields) adds value. Minor improvement would be further condensing the pagination explanation.
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?
Given that an output schema exists (covering return structure), the description adequately explains pagination and returned fields. However, it omits context on authorization requirements (e.g., admin only) and whether the list covers all org members or only those visible to the caller.
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 parameters are already described. The description adds valuable pagination guidance (pass last user_id as 'after_id') and clarifies that 'limit' controls page size. This enriches understanding beyond the basic schema definitions.
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 'List organization members' with a specific verb and resource. It distinguishes from sibling 'list_workspace_members' by indicating organization-level scope, and enumerates the returned fields (id, email, name, role, timestamps).
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?
The description provides no guidance on when to use this tool versus alternatives such as 'list_workspace_members'. It lacks explicit when-to-use, when-not-to-use, or exclusion criteria, leaving the agent to infer scope from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses data freshness but omits rate limits, authentication requirements, or behavior on empty results. Adequate but not exhaustive.
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?
Concise: two sentences for purpose and latency, then bullet-like examples. No filler. Could be slightly more structured (e.g., separate sections) but efficient.
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?
Has output schema, so return format is covered. Description includes usage context, examples, and latency. Lacks details on pagination and error conditions, but overall sufficient for a reporting tool.
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 83%, so baseline is 3. Description adds context via examples and mentions bucketing/grouping, but does not explain each parameter beyond what the schema already provides. Marginal added value.
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 clearly states the tool retrieves detailed token usage from the Messages API and lists return fields (token counts, request counts). It distinguishes from siblings like get_cost_report by emphasizing dimensions and time bucketing, but does not explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides concrete example questions and mentions data latency (~5 minutes). However, it does not state when to avoid using this tool or suggest alternatives for other reporting needs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that certain roles are automatic and workspace_billing cannot be assigned. However, it does not mention the confirmation mechanism or any other behavioral traits like permissions 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.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences with no fluff. The first sentence clearly states the purpose, and the following sentences add essential context. Every sentence is justified.
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?
Has output schema (not shown but available). The description covers the main purpose, exceptions, and a behavioral constraint (workspace_billing inherited). It lacks mention of the 'confirm' parameter's role, but overall is sufficiently complete for a simple add operation.
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 description coverage is 50% (workspace_role and confirm have descriptions). The description adds context about roles (workspace_billing cannot be assigned) but does not describe workspace_id or user_id semantics. It partially compensates for the schema gap.
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 clearly states the verb 'Grant' and the resource 'user access to a workspace'. It distinguishes from siblings like 'invite_member' by implying direct addition, but does not explicitly differentiate from 'invite_member' or 'update_workspace_member_role'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit context: org admins and billing members get automatic roles and don't need to be added, and workspace_billing role is inherited. This guides the agent on when not to use the tool, though it does not mention when to prefer this over 'invite_member'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It clearly describes the tool's behavior: returns daily aggregated user activity, tool usage statistics, and token consumption, and specifies that it is separate from general usage and excludes Bedrock-routed Claude Code. Additional details like pagination or rate limits would improve transparency, but the core behavioral traits are well-covered.
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 three sentences long, with the purpose in the first sentence, details in the second, and an exclusion in the third. No redundant words, clearly structured, and front-loaded. Every sentence adds value.
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?
The tool has 4 parameters, an output schema, and a specific scope. The description covers the tool's domain and output well but lacks guidance on parameter usage (e.g., how to paginate, date format constraints) and does not provide any usage context or error scenarios. Given the output schema exists, completeness is adequate but leaves gaps in practical usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 25% (only 'starting_at' has a description). The description does not add any meaning to the other three parameters ('ending_at', 'limit', 'page'). For a low-coverage schema, the description should compensate by explaining parameter usage, but it does not. The description only describes the output nature, not the inputs.
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 the tool retrieves usage data for Claude Code workspaces, detailing what is returned (daily aggregated user activity, tool usage, token consumption) and explicitly distinguishing it from the general usage report and excluding Bedrock-routed Claude Code. This provides a specific verb+resource and differentiates from siblings like get_usage_report.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for Claude Code workspace data and mentions exclusions (Bedrock-routed), but does not explicitly state when to use this tool over alternatives, nor does it provide clear prerequisites or context for when not to use it. The guidance is implied rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It explicitly states that archived workspaces are hidden, data is preserved, API keys become inactive, and the action is reversible through the Console, providing key behavioral traits beyond the bare operation.
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?
The description is concise (three sentences) and front-loaded with the main action. It could be slightly tighter but avoids unnecessary detail.
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?
Given the presence of an output schema (which presumably documents return values), the description adequately covers the tool's effect on workspace visibility, data, and API keys, making it complete for a simple archive operation.
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 description coverage is 50% (only 'confirm' has a description). The description does not elaborate on 'workspace_id' or provide context beyond the action, so it meets the baseline 3 but adds no extra parameter insight.
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 'Archive a workspace' and explains the consequences (hidden from default listings, data preserved, API keys inactive, reversible), which distinguishes it from siblings like create_workspace, remove_workspace, and update_workspace.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use this tool (to hide a workspace while preserving data) but does not explicitly contrast with remove_workspace or other alternatives, nor does it specify prerequisites or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses key behavioral traits: invite link becomes invalid, invitee not notified, and re-inviting requires a new call. However, it omits the requirement that the 'confirm' parameter must be true (as per input schema), which is a behavioral guardrail.
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?
Three concise sentences, each providing useful information without redundancy. The key action is front-loaded.
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?
Given the simple delete action and presence of an output schema, the description covers most aspects. It correctly notes re-inviting requires a new call. Missing mention of the mandatory confirmation flag (confirm parameter) slightly reduces completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 50% (only 'confirm' has a description). The description adds no parameter-level details; 'invite_id' remains undocumented both in schema and description. The description does not compensate for the low coverage.
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 explicitly states 'Cancel a pending invite', which is a specific verb and resource. It clearly distinguishes from sibling tools like 'invite_member' (create) and 'list_invites' (list).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for canceling a pending invite but does not explicitly guide when to use this tool over alternatives. No when-not or exclusion criteria are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full behavioral burden. It usefully discloses that org admins automatically have workspace_admin but may not appear explicitly, which is a key behavioral nuance. It implies the list is workspace-specific and non-destructive, though it does not mention pagination or rate limits.
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 three concise sentences, front-loading the main action and adding relevant details. Every sentence adds value, with no wasted words.
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?
Given an output schema exists, the description need not explain return values, but it still describes the output fields appropriately. It covers the org admin caveat, which is important for understanding results. It could mention pagination to match the input schema, but overall it is complete for a simple list tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema coverage is 0%, and the description adds no meaning to the parameters (workspace_id, limit, before_id, after_id). It only describes output fields, not input parameters, leaving the agent without guidance on parameter usage beyond schema types.
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 the tool lists members of a specific workspace, providing a specific verb and resource. It distinguishes from sibling tools like 'list_workspace' or 'list_members' by specifying the scope. The detail about output fields (user_id, workspace_role) further clarifies purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description indicates the tool is for listing workspace members, but does not explicitly state when to use it versus alternatives like 'add_workspace_member' or 'invite_member'. It mentions the org admin exclusion but lacks guidance on when not to use the tool or suggestions for other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It discloses that Default Workspace is not listed, archived workspaces don't count against the limit, and the max limit. However, it does not explain pagination behavior (before_id, after_id) or authentication needs, leaving some transparency gaps.
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 concise with three sentences, front-loaded with the purpose. Each sentence provides valuable context without waste.
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?
Given the presence of an output schema, return values are covered. However, the description lacks details on pagination (before_id, after_id usage) and ordering, which are important for a list tool. It adequately covers workspace scoping and limits but misses these behavioral details.
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 description coverage is 25% (only include_archived described). The description partially compensates by explaining the limit context (max 100 active workspaces) and archiving, but before_id and after_id remain unexplained, so it adds limited meaning beyond the schema.
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 'List workspaces in the organization' with specific verb and resource. It distinguishes from sibling tools like create_workspace or archive_workspace by implying it is a read operation, and adds context about the Default Workspace exclusion.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context for when to use the tool (listing workspaces, noting that Default Workspace is excluded and there is a limit of 100 active workspaces). It does not explicitly state when not to use it or suggest alternatives, but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool cannot change admin roles, takes immediate effect, and may impact API keys and workspaces. However, it does not disclose whether the action is reversible, what happens to active sessions, or the requirement for the 'confirm' parameter (though schema covers that). The transparency is adequate but not deeply detailed.
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 two sentences long, front-loaded with purpose, and every sentence adds value. The first sentence states the action, and the second provides constraints and effects. No unnecessary words or repetition.
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?
Given that an output schema exists, the description need not explain return values. It covers the main contextual points: what the tool does, what it cannot do (admin changes), and immediate effects. However, it could mention the confirm parameter's role or provide a usage example, but it's still fairly complete for a tool of this complexity.
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 description coverage is 67%, so baseline is 3. The description does not add meaning beyond what the schema already provides: the role parameter's enum values are listed in both, and user_id and confirm have no additional explanation in the description. Thus, no extra value added.
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 the tool's purpose: 'Change an existing member's organization role.' It uses a specific verb ('change') and resource ('member's organization role'), which distinguishes it from sibling tools like add_workspace_member (adds member) or update_workspace_member_role (workspace-level role change).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly warns when not to use the tool: 'Cannot promote to or demote from "admin" — those changes happen only in the Console.' This provides clear usage boundaries. It also notes immediate effect and potential impact on API keys and workspaces, giving context for when it's appropriate. However, it doesn't compare directly with update_workspace_member_role, leaving some overlap ambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose all behavioral traits. It mentions 'Effective immediately' and clarifies no effect on org role or other workspaces. However, it omits details on permissions, error handling, reversibility, and the purpose of the 'confirm' parameter, which is a safety mechanism.
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 three sentences, front-loaded with the core action, followed by immediate effect and scope limitations. No superfluous information.
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?
The description covers the main purpose and key behavioral aspects. However, it omits explanation of the 'confirm' parameter (a non-obvious requirement), permission prerequisites, and what happens on failure. With an output schema present (not shown), return values are less critical. Overall adequate but could be enriched.
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 description coverage is 50% (2 of 4 params have descriptions). The tool description does not add any parameter-level detail beyond what the schema provides. For instance, it does not explain what workspace_id or user_id represent. Given moderate coverage, description should compensate but fails to do so.
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 'Change a member's role within a workspace,' specifying the verb (change) and resource (member's role). It distinguishes from siblings like 'update_member_role' by noting it does not affect org-level role, implying a separate tool for org roles. The differentiation is effective.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context by stating the change is workspace-specific and does not affect org-level role, guiding the agent to use this for workspace roles. However, it does not explicitly name alternative tools or state when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses currency (USD), client-side conversion from cents, breakdown dimensions, and cost types excluded. It does not mention that the operation is read-only or address potential rate limits, but the provided behavioral context is valuable.
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 100 words, front-loaded with the main function, and each sentence adds value. No redundancy or filler.
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?
Output schema exists, so return values are handled. The description covers key aspects: currency, breakdown, exclusion. Missing is explicit pagination guidance for 'limit' and 'page', which are common parameters requiring explanation for proper use. Overall adequate but with one gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 40%, but the description adds no parameter-specific details. It references 'group_by' implicitly via 'optionally by workspace', but does not explain 'limit', 'page', or 'ending_at' semantics. The agent must rely on the sparse schema descriptions, which are insufficient for correct invocation.
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 'Get dollar-amount cost data for the organization' with specific breakdown by operation description and optional workspace. It provides concrete example questions ('what did we spend last week') and distinguishes from sibling tools by focusing on cost vs. usage.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit usage examples are given, and it clarifies that Priority Tier costs are excluded and should be tracked via 'usage' tool. However, it does not name an alternative tool for that case, leaving the agent to infer from sibling context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavioral traits. It reveals important effects: immediate loss of access, persistence of API keys ('keys are org-scoped, not user-scoped'), and the admin role restriction. This goes beyond the input schema.
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 three sentences, each essential. Front-loaded with the primary action, followed by critical behavioral details, and ending with an important constraint. No wasted words.
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?
Given the tool has 2 parameters and an output schema exists, the description covers the main purpose, key side effects, and a constraint. It is complete enough for an agent to understand the tool's scope and consequences, though it could briefly mention the 'confirm' parameter's role.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 50% (only 'confirm' has a description). The tool description does not add meaning for 'user_id', which remains undocumented. It could clarify the expected format or source of user IDs, but it does not.
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 the action 'Remove a member from the organization' with a specific verb and resource. It distinguishes from sibling tools like remove_workspace_member (which removes from a workspace only) and update_member_role (which changes role instead).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states when NOT to use the tool ('Cannot remove members with the 'admin' role') and directs to an alternative ('that must be done through the Console'). While it doesn't explicitly list other siblings for comparison, the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses key behavioral traits: maximum 100 active workspaces per organization and that creating a workspace does not automatically add members or keys. Could mention if creation is immediate or any rollback behavior.
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 three sentences with no wasted words: first sentence states purpose, second and third add contextual constraints. Front-loaded and efficient.
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?
Given high schema coverage and presence of output schema (indicated by context signals), the description adequately covers creation behavior, limits, and non-automatic side effects. Could mention whether workspace names must be unique.
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%, and the description adds no extra meaning beyond what the schema provides. Baseline score of 3 is appropriate as the schema already documents both parameters (name and confirm) adequately.
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 uses a specific verb ('Create') and resource ('workspace'), clarifies that workspaces partition API keys, members, and limits, and distinguishes from sibling tools like add_workspace_member by noting that creating a workspace does not automatically add members or keys.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear context on when to use (e.g., when you need a new workspace within the 100 active workspace limit) but does not explicitly state when not to use or mention alternative tools like update_workspace.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries full burden. It discloses loss of workspace-specific API key access, that org-level role is unaffected, and that org admins cannot be removed. This covers key behavioral traits but does not mention reversibility or any side effects beyond what is stated.
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 four sentences, front-loaded with the purpose. Every sentence adds value: purpose, consequence, unaffected scope, and limitation. No wasted words.
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?
Given the tool's simplicity (3 params, straightforward action) and presence of an output schema, the description provides adequate context: purpose, consequences, and constraint. It does not mention prerequisites (e.g., user must be a workspace member) or return value, but the output schema likely covers that.
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 low (33%), with only 'confirm' described. The description adds overall context but does not explain workspace_id or user_id individually. However, their purpose is reasonably inferable from the tool name and context. A 3 is appropriate as the description slightly compensates for low schema coverage.
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 'Remove a member from a workspace' with specific verb and resource. It distinguishes from sibling tools like add_workspace_member and update_workspace_member_role by detailing effects on API keys and org-level role, and adds a clear limitation about org admins.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context for when to use (remove from workspace) and includes an exclusion for org admins. However, it does not explicitly compare with the sibling 'remove_member' (likely org-level removal) or state when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses return fields including conditional 'archived_at (if archived),' indicating read-only behavior. Lacks details on error handling or non-existence but is sufficiently clear.
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?
Very concise: three sentences, front-loaded with the core action, and each sentence adds value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple get-by-ID tool with one parameter and an output schema (not shown but referenced), the description covers purpose, usage context, and return fields completely. No gaps.
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 description coverage is 100%, so the schema adequately documents the parameter. The description does not add additional semantic information beyond what is already in the input schema.
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 the tool 'Get a single workspace by ID' and lists the specific fields returned. It distinguishes from sibling 'list_workspaces' by focusing on a single workspace retrieval.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a concrete use case: 'resolving a workspace ID into its display name before referring to it in subsequent operations.' Though it doesn't explicitly mention when not to use it or alternatives, the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully carries the behavioral disclosure burden. It discloses that the tool sends an email, has a 21-day expiration, is non-modifiable, and has role restrictions. This provides sufficient transparency for an agent to understand 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.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences, front-loaded with the main action. Every sentence adds essential information without redundancy.
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?
Given the output schema exists (providing return structure) and no annotations, the description covers key behavioral aspects. It could mention that invites can be deleted via 'delete_invite', but overall it is complete for an invitation tool.
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 the description adds value beyond the schema by explaining expiration, non-modifiability, and the admin restriction. These details help the agent understand the implications of the 'confirm' parameter and the role limitations.
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 the tool invites a new member to the organization, using a specific verb and resource. It distinguishes from siblings like 'add_workspace_member' (workspace-level) and 'delete_invite' (cancellation).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides important usage constraints: invitation expires in 21 days, cannot be modified once created, and cannot grant the 'admin' role. It also directs that admins must be promoted via Console. While it doesn't explicitly contrast with sibling tools, it gives clear context for when to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description implies a read-only operation by noting it returns info, and highlights its safety as a smoke test. Without annotations, it could further state it has no side effects, but the current text is still informative.
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?
Two sentences, no wasted words. The first sentence states the purpose, the second adds practical context. Front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (no parameters, output schema exists), the description is complete. It covers what the tool does, what it returns, and a typical use case.
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?
The tool has zero parameters with 100% schema coverage, so the description does not need to explain parameters. Per calibration, 0 params warrants a baseline of 4.
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 the verb 'get' and the resource 'org info', listing returned fields (ID, name, type). It distinguishes from sibling tools by focusing on organization-level info versus workspace or member operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly mentions a key use case: 'smoke test that the Admin API key is configured correctly.' While it doesn't discuss when not to use it, the context is clear for a simple read tool with no parameters.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Despite no annotations, description discloses key behavioral traits: renaming is cosmetic, deactivation is immediate and one-way, global confirm flag is respected, and reactivation is impossible via this tool. This fully carries the transparency burden.
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?
Four efficient sentences front-loaded with purpose. Every sentence adds value with no redundancy. Structure logically progresses from purpose to details to limitations.
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?
Covers side effects, limitations, and intended actions. Has output schema, so return format not required. Missing error scenarios or prerequisites, but for a mutation with moderate complexity, this is nearly complete.
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 description coverage is 75% (missing api_key_id). Description adds context beyond schema: explains renaming doesn't require confirmation but respects global flag, and that status='inactive' deactivates. Compensates well for schema gaps.
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?
Description clearly states 'Rename or deactivate an API key,' providing a specific verb and resource. It distinguishes from sibling tools (all workspace/member operations) as the only API key mutation tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
States when to use (rename or deactivate) and notes that reactivation must be done in the Console. Lacks explicit when-not conditions, but the context is clear given no alternative API key update tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that changes are cosmetic and do not affect billing, access, or API keys. Could mention validation or failure behavior, but the key behavioral trait is well described.
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?
Two sentences: first states purpose, second clarifies side effects and constraint. No wasted words, front-loaded with core action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given output schema exists, no need to explain return values. Description covers purpose, constraints, and side effects. Complete for a simple update tool.
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 description coverage is 75%. Description adds the constraint that at least one of name or display_color must be provided, which is not in schema. Also clarifies the cosmetic nature, adding meaning beyond the schema.
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 'Rename or recolor a workspace', specifying the verb and resource. It distinguishes from sibling tools like archive_workspace or create_workspace by focusing on cosmetic updates.
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 says 'Cosmetic only — does not affect billing, access, or API keys', guiding when to use (cosmetic changes) and when not. Also states the constraint that at least one of name or display_color must be provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![anthropic-admin-mcp MCP server](https://glama.ai/mcp/servers/Trushtonfactory/anthropic-admin-mcp/badges/card.svg)](https://glama.ai/mcp/servers/Trushtonfactory/anthropic-admin-mcp)

Score Badge

Copy to your README.md:

[![anthropic-admin-mcp MCP server](https://glama.ai/mcp/servers/Trushtonfactory/anthropic-admin-mcp/badges/score.svg)](https://glama.ai/mcp/servers/Trushtonfactory/anthropic-admin-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/Trushtonfactory/anthropic-admin-mcp'

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