Skip to main content
Glama
doitintl

DoiT MCP Server

Official
by doitintl

list_aws_planned_purchases

Read-only

Lists planned AWS commitment purchase projections for an organization, supporting pagination and filtering by service.

Instructions

PerfectScale for Commitments (AWS) — commitment inventory, recommendations, and planned purchases. Returns the laddering projections for the organization — one item per available purchases-projection document (typically compute and/or database; up to four product lines as PS4C expands).

With no filters, returns all existing projection documents for the organization in stable product-line order (compute, then database, then any future lines in enum order). When a filtered product line has no projection document, the response is an empty items array (not 404). Partial projection documents return only the fields available in storage.

404 is returned only when the organization does not exist or the caller cannot access it. An organization that is not onboarded for PS4C still returns 200 with an empty items array when no projection documents exist — use GET /ps4commitments/v1/aws/organizations (or get-by-id) for onboardingStatus.

Pagination: results are returned in stable product-line order (compute, then database, then any future lines in enum order). Use maxResults to limit page size (default 50, max 500). When more items remain, the response includes a non-null pageToken; pass it unchanged on the next request with the same query parameters (service, maxResults). rowCount is the number of items in this page. An invalid pageToken returns 400 with code pagination_token_invalid; an expired token returns 400 with code pagination_token_expired. This endpoint is paginated: to fetch the next page, call again passing the response's pageToken value as the pageToken parameter. Stop once the response has no pageToken — that means there are no more pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceNo
pageTokenNo
maxResultsNo
X-Tenant-IdNo
customerContextNoScope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users.
managementAccountIdYes
Behavior3/5

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

Annotations indicate readOnlyHint and open, so the description's 'returns' aligns with a read operation)Skip. It adds the detail that it returns laddering projections (which conveys the nature of output) but does not specify data freshness, auth requirements, or any side effects. Since annotations already cover the primary behavioral aspects, a middle score is appropriate.

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, front-loaded sentences. First sentence captures the core purpose immediately. Second sentence provides useful nuance about the default behavior and product line scope without unnecessary details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks information about pagination, sorting, output format, and how the optional filter parameters affect the result. It does mention the 'one item per document' detaileb, but does not explain what a 'purchases-projection' document is or how to interpret the returned projection fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is very low (only one required param with no description), but the description explicitly explains what the tool returns and the default behavior (no filters returns all). It adds meaning to the managementAccountId parameter indirectly by scoping to 'the organization', which is the only required param. It compensates well.

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 the tool returns laddering projections for AWS planned purchases, distinguishing it from a generic inventory. It specifies the scope (

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?

"With no filters, returns all existing projections" provides clear context for unfiltered usage, and indicates that filters affect the result set. It doesn't explicitly compare to sibling tools like list_aws_recommendations, but the domain-specific naming and description make the use case fairly distinct.

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/doitintl/doit-mcp-server'

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