MIDAS CIVIL NX tools (MIDAS IT Europe)

Search the MIDAS manuals

midas_docs_search

Read-only

Searches the MIDAS help centre (support.midasuser.com), live: the CIVIL NX and GEN NX online help (every dialog: what it does, where it is in the menus, each input), the MIDAS API (MAPI) JSON manual (every db/ table, its URI, methods, JSON schema and examples), FAQ, tutorials and release notes. Use it to answer how-to and what-does-this-input-mean questions, to check CIVIL NX behaviour before advising, and to find the JSON shape of a MAPI table. English articles. Returns the matching articles (id, title, area, section, snippet, link); read one in full with midas_docs_read. Areas default to CIVIL NX help + API manual + FAQ + tutorials. Needs no model and no account.

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": {
      "query": "<query>"
    },
    "name": "midas_docs_search"
  }
}

Input Schema

Name	Required	Description
`page`	No
`areas`	No	Where to search: civil (CIVIL NX online help), gen (GEN NX online help), api (MIDAS API (MAPI) JSON manual), faq (FAQ), tutorials (Tutorials), updates (Product updates / release notes), cim (CIM online help), excel (Excel Connector), grasshopper (Grasshopper API), or all. Default: civil, api, faq, tutorials.
`limit`	No
`query`	Yes	What to look for, in the manual's own words where possible, e.g. "composite section for construction stage", "moving load optimization", "db/STAG".

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover readOnly and openWorld; the description adds that results are live, English-only, require no model or account, and returns id/title/area/section/snippet/link. It does not mention rate limits or how paging interacts with limits, so not quite maximal.

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?

Front-loaded with what is searched and where, then usage, then return shape and the read follow-up — a logical order. The single block is dense; the parenthetical enumeration of source contents could be tightened, but nothing is redundant.

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

Completeness5/5

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

No output schema exists, yet the description enumerates the returned fields and points to midas_docs_read for full bodies, so an agent knows both what it gets and how to get more. Defaults and scope are covered, leaving nothing essential missing.

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?

With 50% schema coverage the description must compensate, and it does: it restates the default areas set (civil, api, faq, tutorials) and explains what each source is for, plus gives query phrasing guidance. page and limit semantics are left entirely to the schema, so it isn't complete.

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?

States a specific verb (searches) and a precisely enumerated resource (CIVIL NX/GEN NX online help, MAPI JSON manual, FAQ, tutorials, release notes) with the live host named. It explicitly distinguishes itself from sibling midas_docs_read, which it says returns full articles.

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

Usage Guidelines5/5

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

Names concrete use cases (how-to questions, what-does-this-input-mean, checking CIVIL NX behaviour before advising, finding MAPI table JSON shape) and pairs itself with the alternative midas_docs_read for the follow-up step. An agent knows exactly when to reach for this versus the reader.

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

All MIDAS CIVIL NX tools (MIDAS IT Europe) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?