Skip to main content
Glama
nx-ai-bridge

nx-ai-bridge

by qiuyekai

list_expressions

Retrieves the expressions (parameters) of the active NX work part, including each name, value, and formula, so you can inspect model parameters.

Instructions

List the expressions (parameters) of the work part with name, value and formula.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; 'List' implies a non-destructive read, but that is inference rather than declaration. It does disclose what comes back (name, value, formula), yet says nothing about behavior when no part is open, whether results are paginated, or whether expressions are scoped to the part or the session.

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?

A single sentence with the verb and scope front-loaded and the return fields trailing; no filler and nothing redundant.

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 zero-parameter read tool with no output schema, the description is nearly sufficient because it lists the returned fields. The remaining gap is failure/precondition behavior (no open part), which is minor given the tool's simplicity.

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, so the baseline is 4 and there is no parameter meaning left to convey. The description's mention of returned fields is a bonus rather than a substitute for schema detail.

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?

Specific verb ('List') plus resource ('expressions') with a clarifying gloss ('parameters') and an explicit scope ('of the work part'), and it even enumerates the returned fields (name, value, formula). It is clearly separable from set_expression, though it does not name that sibling as the contrasting alternative.

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

Usage Guidelines3/5

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

Usage is only implied: 'of the work part' signals it operates on the currently open part, and 'List' signals a read. There is no explicit when-to-use, no statement of preconditions (e.g. a part must be open), and no named alternative such as set_expression for modification.

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