Skip to main content
Glama

Asset Inventory List

inventory_list
Read-onlyIdempotent

Retrieve a filtered, paginated page of inventory assets by type, search, environment, provider, or source. Use cursor-based pagination to avoid silent truncation.

Instructions

Return a filtered, paginated page of inventory asset rows.

    ``type`` / ``search`` / ``min_severity`` are pushed into the graph store;
    the ``environment`` / ``provider`` / ``source`` facets are matched with a
    bounded keyset refill loop so a filtered page is never silently truncated.
    Page deep with the returned ``pagination.next_cursor``. Findings never
    appear in the list.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoComma-separated asset entity types to include, e.g. 'agent,cloud_resource'. Finding types are rejected.
limitNoMaximum asset rows to return (1-200).
cursorNoOpaque keyset cursor from a previous page's pagination.next_cursor.
offsetNoPagination offset for non-cursor paging.
searchNoFree-text search over asset name / label / attributes.
sourceNoFilter by data-source / provenance facet.
scan_idNoOptional graph scan ID. Omit to use the latest snapshot.
providerNoFilter by provider facet, e.g. 'aws', 'snowflake'.
tenant_idNoTenant scope for the snapshot. Defaults to 'default'.default
environmentNoFilter by environment facet, e.g. 'production'.
min_severityNoMinimum severity floor for included assets: critical / high / medium / low.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations (readOnlyHint, idempotentHint) already indicate safety. The description adds valuable behavioral context: 'Findings never appear', explanation of push-vs-keyset filtering, and pagination using next_cursor. No contradictions.

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?

The description is concise (four sentences), front-loads the main purpose, and avoids redundancy. Each sentence adds unique value without extraneous detail.

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, the description covers key points: pagination, filtering behavior, and exclusion of findings. Minor gaps exist (e.g., error handling), but overall sufficient for a read-only tool.

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% with descriptions for all parameters. The description adds minimal extra meaning (e.g., 'type/search/min_severity are pushed into graph store') but mostly restates schema info. Baseline 3 is appropriate.

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?

The description clearly states 'Return a filtered, paginated page of inventory asset rows', specifying the verb and resource. It further clarifies that findings are excluded, but does not differentiate from siblings like 'inventory' or 'search' tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'search' or 'inventory_summary'. The description focuses on internal mechanics rather than usage context.

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