Aalto

Get collection context

aalto_get_collection_context

Read-onlyIdempotent

Returns a collection's budget roll-up (spent is quantity × price across all statuses, in the budget's currency only; when the project shows tax it is the ex or inc tax total and tax_basis says which; unconverted_items counts products left out because they have no price or are in another currency, which is never converted), product status counts (products only, not inspiration), sections, the workspace tax setup, and a page of its items. Call before suggesting products for a room so spend, sections and what is already saved are known, and before exporting a schedule with tax. Use the cursor to page through large collections.

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": {
      "collection_id": "<collection_id>"
    },
    "name": "aalto_get_collection_context"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`cursor`	No
`format`	No	concise
`collection_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), so the description rightly spends its words on data semantics: how spent is computed, what tax_basis means, and that unconverted_items counts excluded products that are never converted. It also notes cursor pagination, though it omits rate limits or permission needs.

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 the return contents, then the usage conditions, then pagination. The long nested parenthetical about spent/tax/unconverted_items is information-dense but heavy within an otherwise efficient note.

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 does the necessary work of explaining what comes back and how the spend figures are derived. It is incomplete only on the format and limit parameters needed to control the response.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter burden. It explains cursor ('page through large collections') and implies page size via 'a page of its items', but the format enum (concise/detailed) and the limit bounds 1-50 are never mentioned.

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 precise verb and resource and enumerates the returned components: budget roll-up, status counts, sections, workspace tax setup, and a page of items. It also draws a clear boundary (product status counts are 'products only, not inspiration'), which no sibling tool covers.

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?

Gives two concrete call-before conditions ('before suggesting products for a room' and 'before exporting a schedule with tax') that implicitly route to aalto_find_similar/aalto_create_products and aalto_export_collection. It stops short of naming those siblings or stating when not to use it.

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

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

Resources

Need Help?