MCP para Primavera Unifier

unifier_list_shells

Retrieve a paginated list of Primavera Unifier shells or projects by type, status, or filter, returning items, total, and summary; use total for exact counts.

Instructions

Lista proyectos/shells de Unifier mediante V1 admin/projectshell. Devuelve una página de items, total y summary; usa total para el recuento exacto y no enumeres más elementos de los incluidos en items.

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": "unifier_list_shells"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No
`limit`	No
`offset`	No
`status`	No
`filter_condition`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 16, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose real behavior: the response is paginated ('una página de items') and includes total and summary, plus the constraint not to enumerate beyond items. It omits auth/permission requirements, rate limits, and any note on what filtering is applied by default.

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?

Two tight sentences, both front-loaded: capabilities first, then the result-count caveat. No filler, though the output caveat could have been merged into the first sentence.

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?

Absent an output schema, the description usefully sketches the return shape (items/total/summary) and the pagination model. But for a tool with five undocumented parameters and no annotations, it leaves too much unsaid about inputs and filtering to be considered complete.

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% for five parameters, and the description never mentions type, limit, offset, status, or filter_condition. Only the word 'página' indirectly hints at limit/offset, leaving the enum values and filter syntax entirely unexplained.

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?

States a specific verb and resource ('Lista proyectos/shells de Unifier') and even names the underlying API surface (V1 admin/projectshell), so the agent knows exactly what is returned. It does not, however, differentiate itself from siblings such as unifier_audit_inactive_shells or unifier_read_shell_360.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is about interpreting results ('usa total para el recuento exacto'), not about when to choose this tool over the other shell-related siblings. There are no prerequisites, no exclusions, and no named alternatives.

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

Deploy Server