Skip to main content
Glama

Export a collection

aalto_export_collection

Exports one collection as a CSV, an Excel spreadsheet (.xls) or a PDF lookbook and returns a download link valid for 15 minutes. Pass tax_display ("both" for ex tax, tax and inc tax) for an FF&E schedule with VAT, GST or sales tax columns; that needs a Tax region set in the workspace (see aalto_whoami). It creates a temporary file only; nothing in the library changes. Limited to 20 exports per user per UTC day, and an export that fails still counts toward that limit. Excel and PDF need the Personal or Team plan.

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_export_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNocsv
tax_displayNoTax columns (VAT, GST or sales tax): "exclusive", "inclusive" or "both" add them even when the project hides tax; "off" leaves them out. Omit to use the project's setting. Needs a Tax region set for the workspace.
collection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the export creates only a temporary file and changes nothing in the library (reconciling the readOnlyHint=false), the link expires in 15 minutes, a 20-per-UTC-day cap applies, failures still consume quota, and Excel/PDF require Personal or Team. That is exactly the operational detail annotations cannot carry.

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?

Three tight sentences, front-loaded with what is produced and returned before the conditional tax_display detail and the quota/plan caveats. No filler sentences; each clause carries new information.

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 no output schema, the description supplies the missing return contract (download link, 15-minute validity) and the failure/quota semantics. For a non-destructive, single-purpose export tool with a small schema, nothing an agent needs before calling it is absent.

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

Parameters4/5

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

Schema coverage is only 33%, but the description compensates: it explains tax_display's "both" value and its dependency on a workspace Tax region, and enumerates the three export formats. collection_id is not described anywhere, though its uuid type and required status make it self-evident.

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 (exports) and resource (one collection) plus the three output formats and that it returns a time-limited download link. No sibling tool does anything similar, so the agent can distinguish it immediately from list/get/organize tools.

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 clear conditions for the optional tax_display parameter, points to aalto_whoami for the workspace Tax region, and gates formats by plan. It stops short of naming an alternative path for agents on the Free plan or those who hit the 20/day limit, but the when-to-use context is strong.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources