Omnara

List project machine pool grants

grant_pools_list

Read-onlyIdempotent

Lists the machine pools a project can create machines from, one grant per pool, most recently granted first by default.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "orgID": "<orgID>",
      "projectID": "<projectID>"
    },
    "name": "grant_pools_list"
  }
}

Input Schema

Name	Required	Description
`name`	No	Case-insensitive glob over the list's logical name. `*` matches zero or more characters, `?` matches one character, and `\` escapes a wildcard.
`sort`	No	Sort order for named resources that expose created and modified timestamps.
`limit`	No	Maximum number of items to return in one page.
`orgID`	Yes	Organization ID (org_...).
`cursor`	No	Opaque pagination cursor from a previous response's next_cursor. Omit for the first page.
`projectID`	Yes	Project ID (proj_...).
`machine_pool_id`	No	Return only the grant for this machine pool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026
- addedInput schema / properties / orgID / description
```
Added value: +"Organization ID (org_...)."
```
- addedInput schema / properties / projectID / description
```
Added value: +"Project ID (proj_...)."
```

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / machine_pool_id

Added value: +{
+  "description": "Return only the grant for this machine pool.",
+  "pattern": "^mpo_[a-z2-7]{26}$",
+  "type": "string"
+}

First observedOct 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond structured fields: one grant per pool and default ordering most-recently-granted-first. It stops short of richer behavioral detail such as pagination or failure modes.

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?

A single, front-loaded sentence that establishes the resource and the key behavioral default with no 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?

With no output schema, the description conveys what is returned (one grant per pool) and the default ordering, which covers the essentials for a list tool. It omits detail about the shape of a grant record, but the sibling grant_pools_get covers that.

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%, so the schema already documents all seven parameters (name glob, sort enum, limit, cursor, IDs). The description adds no parameter-level detail, which is the correct baseline when the schema does the heavy lifting.

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 states a specific verb (Lists) and resource (machine pool grants a project can create machines from), which is clear enough to separate it from grant_pools_add/get/delete. It does not explicitly name those siblings, but the semantics of 'grant' vs 'get' is discernible.

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?

Usage is implied by the list-nature of the endpoint, but there is no explicit when-to-use or when-not-to-use guidance, nor any pointer to grant_pools_get for a single grant. The default ordering note hints at default behavior but not selection criteria.

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

All Omnara tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.