Voila Groceries MCP

Get Completed Orders

voila_get_completed_orders

Read-onlyIdempotent

Retrieve completed Voila orders using cursor pagination to manage large transaction histories. Enables authenticated users to browse order history efficiently.

Instructions

Fetch completed Voila orders with cursor pagination for the authenticated account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "voila_get_completed_orders"
  }
}

Input Schema

Name	Required	Description	Default
`pageSize`	No
`pageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 4, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds cursor pagination detail beyond annotations, but does not disclose other behavioral traits like rate limits, ordering of results, or response structure.

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?

The description is a single sentence that conveys the essential information without any redundancy or unnecessary words. It is front-loaded with the key action.

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?

Given the tool's simplicity (2 optional params, no output schema, safe annotations), the description covers the core behavior. However, it lacks information about default ordering or response format, which would be helpful for a complete understanding.

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 has 0% description coverage for both parameters. The description mentions 'cursor pagination', implicitly clarifying that pageToken is a cursor, but does not explain pageSize (e.g., default value, behavior when omitted). This provides some value but insufficiently compensates for the missing schema descriptions.

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?

The description clearly states the verb 'fetch', the resource 'completed Voila orders', and includes scope ('for the authenticated account') and pagination method ('cursor pagination'). This distinguishes it from sibling tools like voila_get_completed_order_items or voila_get_order_details.

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?

The description implies usage (fetching completed orders), but it does not explicitly mention when to use this tool versus alternatives such as voila_get_order_details or voila_get_completed_order_items. No when-not-to-use guidance is provided.

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

Deploy Server