Skip to main content
Glama
Sign In
MCP para Primavera Unifier

MCP para Primavera Unifier

by jbrasero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

unifier_connection_test

Verify REST access and confirm the Primavera Unifier shells listing returns valid JSON, helping diagnose authentication or connectivity issues.

Instructions

Verifica acceso REST y una respuesta JSON válida del listado de shells.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool validates REST access and JSON validity, which is useful, but says nothing about authentication requirements, side effects, rate limits, timeout behavior, or what a failed verification returns.

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?

A single, front-loaded sentence with no filler or redundancy. It is efficient, though extremely terse.

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?

For a zero-parameter diagnostic, the description covers what is checked but not the success/failure outcome shape, and no output schema exists to compensate. Given the tool's simplicity the gap is moderate rather than severe.

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?

The tool takes zero parameters, which establishes a baseline of 4. The description correctly implies no input is needed to trigger the check.

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 (verifica) and object (acceso REST y una respuesta JSON válida del listado de shells), so an agent can tell this is a connectivity/response-validation check rather than a data-fetch tool. It does not, however, name or distinguish itself from the closest siblings such as unifier_list_shells or unifier_rest_request.

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?

There is no when-to-use guidance, no statement of prerequisites, and no routing to alternatives like unifier_list_shells (the actual listing call) or unifier_rest_request. Usage must be inferred purely from the wording 'verifica'.

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

Deploy Server

Other Tools