Skip to main content
Glama

List principals of this deployment

list_principals
Read-only

Lists tenant principals with IDs, names, roles, and disabled status so admins can audit access and identify inactive accounts; API keys are never exposed.

Instructions

Admin only. List your tenant's principals — id, name, roles, and whether disabled (the deployment operator sees every tenant's). Never shows API keys (only their hashes are stored).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_principals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already mark this as a read-only, closed-world operation, so the description adds genuine beyond-schema context: the admin-only access requirement, the tenant-vs-operator scoping difference, and the disclosure limit that API keys are never returned because only hashes are stored. That last point is valuable for an agent deciding whether this call can answer a credential question.

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?

Front-loads the critical constraint ('Admin only') and then states what is returned and what is withheld. Two sentences, no filler, though the parenthetical about the operator view interrupts the return-field list slightly.

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?

An output schema already exists, so return format need not be explained, and the description fills the remaining gaps an agent needs: access tier, visibility scope, and the sensitive-data exclusion. Nothing essential for calling it correctly appears to be missing.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly avoids inventing parameters and instead spends its words on scope and access.

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?

Names a specific verb and resource (list principals) and enumerates the fields returned (id, name, roles, disabled), so an agent knows exactly what comes back. It also distinguishes the tenant-scoped view from the operator view. It does not differentiate itself from siblings like create_principal or revoke_principal by name, which keeps it short of a 5.

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 prerequisite 'Admin only' is stated, which is real usage guidance. But there is no explicit routing to alternatives (e.g., use create_principal to add one, revoke_principal to disable), so the when-to-use condition is implied rather than spelled out.

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