ARCNM

List Environments

list_environments

Read-onlyIdempotent

List the organization's costing environments, newest first. Each one is a set of machines, rates and overheads for a plant, a supplier or a region. Use it to find the environment id to price a part in. Without one, upload_and_quote and quote_part use the organization's default environment. Page with cursor until has_more is false. Read-only and free.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum rows to return in one page.
`order`	No	Sort direction over the collection's ordering key. Use `asc` to reconcile a batch: rows come oldest-first, so work created while you page lands after your position instead of shifting rows under it.	desc
`cursor`	No	Opaque position token from the previous page's `next_cursor` (or the `Link` / `X-Next-Cursor` response header). Omit it for the first page. Keep every other query parameter identical for the whole walk — a cursor replayed against different filters is rejected.
`offset`	No	Rows to skip. Superseded by `cursor`, which is stable under concurrent writes; kept for existing integrations. Bounded — past the cap, page with `cursor`.
`created_after`	No	Only rows created at or after this instant (RFC 3339, e.g. `2026-07-20T09:00:00Z`). Inclusive.
`created_before`	No	Only rows created strictly before this instant (RFC 3339). Exclusive, so an `after`/`before` pair tiles a range without overlap.

Output Schema

Name	Required	Description
`data`	Yes	This page's rows, in the order and shape the REST list returns them.
`has_more`	Yes	False on the last page. Stop on this, never on a short page.
`next_cursor`	Yes	Pass as `cursor` to read the next page. Null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
AddedOct 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description reinforces this with 'Read-only and free' — 'free' adds quota-relevant context not present in the annotations. It also discloses pagination behavior ('Page with cursor until has_more is false'), which is genuinely useful beyond the structured fields, though it doesn't detail rate limits or default page size.

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?

Front-loaded with purpose, then identity, then usage routing, then paging mechanics — a good ordering with no wasted sentences. 'Read-only and free' is mildly redundant with the readOnlyHint annotation, which keeps it from a 5.

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?

With an output schema present, the description needn't document return values, and it still covers purpose, sibling routing, the default-environment fallback, and the cursor walk. Nothing an agent needs to call this correctly is missing.

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% and the parameter docs are unusually rich (order explains the reconciliation use of `asc`, cursor explains the replay/rejection rule), so the schema does the heavy lifting. The description only gestures at paging via cursor and adds no syntax beyond that, making the baseline 3 appropriate.

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?

States a specific verb and resource ('List the organization's costing environments') plus the ordering ('newest first') and what an environment actually is ('a set of machines, rates and overheads for a plant, a supplier or a region'). No sibling tool lists environments, so the agent can distinguish this immediately.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('find the environment id to price a part in') and names the downstream alternatives with the fallback condition: 'Without one, upload_and_quote and quote_part use the organization's default environment.' This routes the agent correctly without any inference.

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

All ARCNM 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.