LS-PrePost-MCP

by lwz20210407

Overview Schema Source Related Servers Discussions Admin

list_nodes

Retrieve paginated native user node IDs and reference coordinates for a specified model, using a zero-based offset. Coordinates are returned undeformed.

Instructions

Page native user node IDs and reference coordinates. Offset is zero-based; coordinates are not deformed.

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": {
      "model": "<model>"
    },
    "name": "list_nodes"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`model`	Yes
`offset`	No
`file_type`	No	keyword

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 30, 2026

TDQS

C2.9/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 behavioral burden, and it does disclose two non-obvious traits: offset is zero-based and returned coordinates are undeformed (reference coordinates). It still omits pagination behavior beyond offset, ordering guarantees, and any auth/scope requirements.

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 with the core listing behavior front-loaded and no filler. Slightly under-specified rather than bloated, but structurally efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paginated listing tool with no annotations, no output schema, and 0% parameter coverage, the description is thin: it never describes the returned shape (e.g., ID-to-coordinate mapping) or pagination termination. An agent cannot confidently call it without guessing at model/file_type semantics.

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% across four parameters, so the description must compensate but only covers one: it explains 'offset is zero-based' but adds no meaning for model, limit, or the ambiguous file_type (default 'keyword'). Two of four parameters remain entirely undocumented.

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 description states a specific verb ('Page') and resource ('native user node IDs and reference coordinates'), so the agent knows this lists nodes and their coordinates. It is clear on its own, but does not differentiate from siblings such as list_parts or extract_d3plot_nodal, leaving the agent to infer boundaries.

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 prerequisites, and no mention of alternatives among the many sibling listing/extraction tools. The agent gets no routing help for choosing list_nodes over extract_d3plot_nodal or get_element_connectivity.

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