Skip to main content
Glama
Sign In
FDTD Lumerical MCP

FDTD Lumerical MCP

by pcmdagonger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

result_get

Read a specific result dataset from a named FDTD object by providing the object and result names.

Instructions

Read a result dataset from a named FDTD object.

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": {
      "object_name": "<object_name>",
      "result_name": "<result_name>"
    },
    "name": "result_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_nameYes
result_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Indicates a read operation but provides no additional behavioral details (e.g., side effects, authorization, error conditions). With no annotations, the description fails to disclose important aspects beyond the basic verb.

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?

Single sentence with no unnecessary words, but lacks structure (e.g., no sections or bullet points) that could improve readability. Still, it is front-loaded with the key action.

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?

Given two required parameters and no parameter descriptions, the description is incomplete. An output schema exists but doesn't compensate for the lack of parameter guidance and usage context.

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%, and the description does not explain the meaning of object_name or result_name. The schema only provides types; without context, an agent cannot understand what values to provide.

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?

Description states verb 'Read' and resource 'result dataset from a named FDTD object', which is specific and distinguishes from sibling tools like object_get (reads object properties) and data_export (exports data). However, it could explicitly contrast with similar read tools.

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?

No guidance on when to use this tool vs alternatives like object_get or data_export. Lacks any context on prerequisites, such as requiring the object to exist and have results.

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

Deploy Server

Other Tools