Skip to main content
Glama
Sign In

Primavera

by com.primaverapp
OverviewDiscussionsAdmin

Complete a list

complete_list
Idempotent

Add places to a list from its original search; places already in the list are skipped. Priced as an export: 1 credit per place never delivered to the account (Agency: included under fair use).

Paid: maxCredits (the most credits this call may spend, never exceeded) and idempotencyKey (a new UUID v4 for this operation) are required; without them nothing runs. To retry after an error or a timeout, send the same idempotencyKey with the same arguments: nothing is charged twice. Ask the user before calling it.

Same call as POST /api/v1/lists/{id}/complete of the REST API.

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": {
      "listId": "<listId>",
      "rows": "<rows>",
      "maxCredits": "<maxCredits>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "complete_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesPlaces to add from the original search (places already in the list are skipped).
listIdYesId of a list of the account (from create_list or list_lists).
maxCreditsYesThe most credits this call may spend (required on every paid call, with an Idempotency-Key header). Never exceeded.
idempotencyKeyYesA new UUID v4 for this operation (sent as the Idempotency-Key of the API). Reuse it only to retry the very same call: the saved result comes back, nothing is charged twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare the safety profile (non-readonly, non-destructive, idempotent, non-open-world). The description adds pricing (1 credit per never-delivered place, Agency fair use), the hard requirement for maxCredits/idempotencyKey ('without them nothing runs'), and exact retry semantics where no double charge occurs. That is the kind of behavioral 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, then pricing, then the paid-call requirements, then retry behavior, then the REST equivalence. Sentences earn their place, but the terse 'Paid:' fragment and the line break make the middle slightly harder to parse than it needs to be.

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?

For a paid mutation with four required params and no output schema, the description covers cost, confirmation, required fields, and retry safety. It does not explain what the call returns or whether the addition is synchronous versus job-based, which is the main remaining gap.

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 coverage is 100% and every parameter already has a description, so baseline is 3. The prose mostly restates requiredness and maxCredits/idempotencyKey semantics rather than adding new meaning, though 'never exceeded' and 'without them nothing runs' reinforce the consequence of misusing them.

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 definition opens with a specific verb and resource: adding places to a list from its original search, with the skip-if-already-present rule. That is distinguishable from create_list (which makes a list) and get_list_items (which reads them). It stops short of naming a sibling alternative the way a 5 would.

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?

It gives a strong operational condition: 'Ask the user before calling it,' plus that the call is paid and cannot run without maxCredits and idempotencyKey. It does not say when to prefer this over estimate_list or start_list_job, so alternatives are left implicit.

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

All Primavera toolsInspect
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