Skip to main content
Glama
Sign In
Petra Security MCP Server

Petra Security MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

petra_list_tenants

Read-onlyIdempotent

Lists every client tenant in the Petra organization with tenant IDs, Microsoft tenant ID, onboarding date and paused status. Start here to find the tenantId other Petra tools require.

Instructions

List every client tenant (Microsoft 365 customer) in the Petra organization, alphabetically, with its Petra tenant ID, Microsoft tenant ID, onboarding date and paused flag. Start here to find the tenantId other petra_* tools take. Removed tenants are excluded; paused tenants are included unless includePaused is false.

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": "petra_list_tenants"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameContainsNoCase-insensitive substring match on the tenant name (filtered locally; Petra has no search parameter).
includePausedNoInclude tenants whose ingestion is paused. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description goes beyond them by stating the sort order (alphabetical), the exclusion of removed tenants, and the default inclusion of paused tenants — behavior an agent could not infer from the annotations.

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?

Three tight sentences, front-loaded with the core operation and returned fields before the workflow hint and the exclusion caveat. No filler, though the includePaused clause partially duplicates the schema default already stated.

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 two-optional-parameter list tool with no output schema, the description compensates by naming the returned fields, the ordering, and the filtering defaults. An agent has everything needed to select and call it correctly.

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%, with both parameters documented including the includePaused default, so the schema already does the work. The description reinforces the includePaused default in prose but says nothing about nameContains's local-substring semantics, which the schema covers instead. Baseline 3 applies.

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?

Names a specific verb and resource ('List every client tenant'), defines tenant as a Microsoft 365 customer, and enumerates exactly what is returned (Petra tenant ID, Microsoft tenant ID, onboarding date, paused flag). That level of specificity makes it unmistakable against siblings like petra_list_incidents or petra_get_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?

'Start here to find the tenantId other petra_* tools take' gives explicit entry-point guidance tied to the rest of the tool family, plus a stated exclusion rule for removed tenants. It stops short of naming a concrete alternative or a when-not-to-use case, which keeps it just below the top score.

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