Skip to main content
Glama
Sign In
FDTD Lumerical MCP

FDTD Lumerical MCP

by pcmdagonger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

object_get

Read selected properties from a named FDTD object in Lumerical simulations to retrieve specific values for analysis or scripting.

Instructions

Read selected properties 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": {
      "name": "<name>"
    },
    "name": "object_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
propertiesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It only indicates a read operation, but fails to disclose behavioral traits like error handling, authorization requirements, or the effect of missing properties.

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?

The description is a single concise sentence that front-loads the action and resource. However, it is overly terse, sacrificing necessary detail for brevity.

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 the low schema coverage and missing behavioral details, the description is inadequate for an agent to reliably invoke the tool. It does not explain the required 'name' format or the effect of omitting 'properties'.

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%, yet the description adds no explanation of the 'name' or 'properties' parameters. It implies the 'properties' parameter selects fields but does not clarify default behavior (e.g., whether null returns all properties).

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?

The description clearly states the verb 'Read' and the resource 'selected properties from a named FDTD object', which effectively distinguishes it from sibling write tools like object_add, object_delete, and object_set.

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 is provided on when to use this tool versus alternatives such as result_get or object_set. The description lacks context for appropriate usage scenarios or exclusions.

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