Skip to main content
Glama
msaad00

agent-bom

by msaad00
OverviewSchemaRelated ServersScoreDiscussions
Python

Access Review

access_review
Read-onlyIdempotent

Retrieve NHI access-review campaigns and their status. Optionally fetch details of a specific campaign by ID, or list all campaigns with overdue statuses.

Instructions

List or get NHI access-review / recertification campaigns and their status.

    Read-only: pass ``campaign_id`` to fetch one campaign with its review
    items, or omit it to list campaigns (overdue statuses refreshed).
    Creating a campaign or submitting a reviewer decision is a write action
    and is intentionally not exposed through this read-only tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idNoOptional campaign id to fetch one campaign with its review items. Omit to list campaigns.
tenant_idNoTenant scope to read. Defaults to the control-plane default tenant.default
limitNoMaximum campaigns to list when campaign_id is omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Reinforces read-only nature from annotations. Adds detail about refreshing overdue statuses when listing. Consistently describes behavior. No contradictions 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?

Three sentences, no wasted words. Front-loaded with purpose. Each sentence adds critical 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?

Covers main use cases fully. Could mention pagination behavior for limit parameter. Output schema exists so return values not needed.

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 100%. Description adds value by explaining dual mode (campaign_id vs omit). Provides usage context beyond schema descriptions.

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 'List or get NHI access-review / recertification campaigns and their status.' Specifies two modes: listing all or fetching one campaign. Distinct from sibling tools like identity_revoke or policy_check.

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?

Explicitly states when to use (read-only) and when not to use (write actions like creating/submitting). Provides clear param guidance. Lacks explicit naming of alternative tools for write actions.

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