Skip to main content
Glama

NHI Discover

nhi_discover
Read-onlyIdempotent

Discover non-human identities from Okta and Entra IdP providers. Returns normalized metadata including id, name, owner, created, credential expiry, and scope references.

Instructions

Discover non-human identities (Okta service apps / Entra service principals).

    Read-only and reference-only: returns normalized identity metadata (id,
    name, owner, created, credential expiry, scope references) — never secret
    material. Each provider is gated by its own discovery env flag and token;
    a disabled or unconfigured provider is reported in ``providers`` with a
    clear status rather than failing the request.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providersNoComma-separated IdP providers to query: okta, entra. Omit to query both.
tenant_idNoTenant scope for the response envelope. Defaults to the control-plane default tenant.default

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds that it never returns secret material and explains graceful degradation for disabled providers, providing useful behavioral context beyond 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 concise sentences front-load the core purpose and add relevant behavioral details without 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 presence of an output schema and comprehensive annotations, the description covers key aspects: what is returned, safety guarantees, and error handling. Could mention pagination or limits but not necessary for this use case.

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%, so the description adds minimal new meaning beyond the schema descriptions. It mentions provider gating but does not elaborate on parameters.

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 discovers non-human identities (Okta service apps / Entra service principals) with a specific verb and resource. It distinguishes from sibling tools that target different domains or actions.

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?

Provides usage context: read-only, reference-only, and explains provider gating and error handling. However, it does not explicitly state when to use versus alternatives or when not to use.

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/msaad00/agent-bom'

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