Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_mcp_server_user_access

Read-onlyIdempotent

List per-user access for an MCP server to audit permissions. Returns default access mode, override flags, and connection status so you can review who can use it before updating access.

Instructions

List per-user access for an MCP server. Returns the default access mode, override flags, and connection status so you can audit who can use it; use before update_mcp_server_user_access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe MCP server ID or slug
page_sizeNoNumber of results per page (max 100)
current_pageNoZero-based page number; the first page is 0

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.11.5
    • changedInput schema / properties / current_page / description
      Previous value: -"Page number for pagination"New value: +"Zero-based page number; the first page is 0"
    • removedInput schema / properties / current_page / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / current_page / minimum
      Added value: +0
  2. Changed3 schema fields changedv0.5.0
    • addedInput schema / properties / current_page / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / current_page / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / page_size / type
      Previous value: -"number"New value: +"integer"
  3. Changed2 schema fields changedv0.3.7
    • addedInput schema / properties / current_page
      Added value: +{
+  "description": "Page number for pagination",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / page_size
      Added value: +{
+  "description": "Number of results per page (max 100)",
+  "exclusiveMinimum": 0,
+  "maximum": 100,
+  "type": "number"
+}
  4. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds value beyond annotations by disclosing what the response reveals (default access mode, override flags, connection status) and that it serves an audit purpose. No contradiction with annotations.

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 with zero filler. The verb+resource is front-loaded, followed by the return-value context and the usage-order hint. Every clause earns its place.

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?

For a read-only list tool with full schema coverage, annotations, and an output schema, the description covers purpose, response contents, and usage ordering. Pagination and return structure are handled by the schema/output schema, so nothing critical is missing. A small gap: it doesn't hint at scale or how open-world results should be interpreted, but annotations cover 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 description coverage is 100% — id, page_size, and current_page are all documented in the schema with type and semantics. The description does not add param-level detail, but it doesn't need to; the baseline of 3 applies when the schema does the heavy lifting.

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 states a specific verb+resource: "List per-user access for an MCP server." This clearly distinguishes it from sibling tools like list_mcp_servers (listing servers themselves), get_mcp_server (fetching a single server), and list_mcp_server_capabilities/connections (other server dimensions). An agent can tell it apart without opening schemas.

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 gives clear context — "audit who can use it" — and explicitly names the follow-on tool update_mcp_server_user_access with the ordering "use before." It lacks explicit when-not guidance for the other list_mcp_server* siblings, but the main alternative is named and the audit scenario is concrete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools