aras-plm-mcp

aras_get_list_values

Retrieve allowed values for list-type properties of an Aras ItemType before creating items, ensuring schema validation passes and preventing rejected or ignored values.

Instructions

Valori AMMESSI dalle proprieta' di tipo lista di un ItemType (es. make_buy, unit, drawing_size). Da chiamare PRIMA di creare: un valore fuori lista supera la validazione dello schema — il nome della proprieta' esiste — ma viene rifiutato o ignorato da Aras.

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": {
      "itemType": "<itemType>"
    },
    "name": "aras_get_list_values"
  }
}

Input Schema

Name	Required	Description	Default
`itemType`	Yes	es. 'Part', 'Document'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 23, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses a critical behavior: out-of-list values appear valid to the schema but fail in Aras. However, it does not describe the return format (e.g., a list of values per property, a flat list, etc.) or any other behavioral nuances like error handling. While the warning is valuable, the disclosure is incomplete given the absence of annotations.

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 two sentences with zero wasted words. The purpose is front-loaded, and the critical usage warning is included efficiently. It is exemplary in conciseness and structural clarity.

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?

The description covers the core functionality and the validation caveat, but does not explain the return format or any limitations (e.g., does it return values for all list properties or only a specific one?). For a simple one-parameter tool with no output schema, this is a noticeable omission. The description is adequate but not fully complete.

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?

The input schema already describes itemType with examples ('Part', 'Document'), and the description adds contextual meaning (it is used to fetch list values for that item type) but does not go beyond the schema. Since schema description coverage is 100%, a baseline score of 3 is appropriate—the description adds no further parameter-level detail.

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 tool returns allowed values from list-type properties of an ItemType, with concrete examples (make_buy, unit, drawing_size). It is specific about the resource (list properties) and the action, and no sibling tool appears to serve this specific purpose, so it is easily distinguishable.

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?

The description explicitly instructs to call this tool BEFORE creating an item, and explains why: out-of-list values pass schema validation but are rejected or ignored by Aras. This provides a clear usage context. It does not mention alternatives or exclusions, but the guidance is sufficient for correct invocation.

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

Deploy Server