NovaSolver Studio MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

genesis_result

Read-onlyIdempotent

Retrieves Genesis run results by case ID, including kept volume, thinnest member, compliance or temperature rise, convergence history, warnings, and STL download path.

Instructions

Result of the latest (or given) Genesis run: kept volume, measured thinnest member, compliance or temperature rise, convergence, warnings, the convergence history and the STL download path.

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": {
      "case_id": "<case_id>"
    },
    "name": "genesis_result"
  }
}

Input Schema

Name	Required	Default
`run_id`	No
`case_id`	Yes
`language`	No	ja

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.0Nov 13, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The annotations already declare this to be a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context by specifying the returned result fields, including convergence history and STL download path, which is valuable because no output schema exists.

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 a single front-loaded sentence with a colon-delimited list of returned items. Every element earns its place by describing the result contents, with no filler or redundancy.

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 adequately covers the return contents for a read-only result retrieval tool and annotations cover the safety profile. However, with zero schema description coverage, it leaves all three parameters unexplained and provides no guidance on error conditions or when to prefer sibling tools.

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%, so the description must carry the burden of explaining the three parameters. It only vaguely implies that run_id may be optional via 'latest (or given)' and does not explain case_id, run_id semantics, or the language parameter.

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 clearly identifies this as a retrieval tool for the result of a Genesis run and enumerates the specific outputs returned. It does not explicitly distinguish itself from sibling result-related tools such as get_results or probe_results.

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?

The phrase 'latest (or given) Genesis run' implies usage after a Genesis run, but there is no explicit guidance on when to use this tool versus alternatives like get_results, probe_results, or check_convergence. No exclusions or selection criteria are given.

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