zemax_get_configuration_operandsRetrieves multi-configuration editor operands and values across configurations in Zemax OpticStudio for analysis and editing. Optionally specify row range to limit results.
Get MCE operands and values across configurations.
| Name | Required | Description | Default |
|---|---|---|---|
| endRow | No | Last row; 0 means all | |
| startRow | No | First row |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Get' implies a read, but nothing is said about whether a file must be open, how these differ from a configuration summary, or how large result sets are bounded. The endRow=0 convention is left to the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no filler, front-loaded with the action and resource. Nothing wasted, nothing buried.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter read tool with no output schema and no annotations, the description conveys the gist but omits what the returned operand/value structure looks like and whether results are paginated by row. Adequate but not fully self-sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so startRow/endRow semantics are fully documented in the schema and the baseline is 3. The description adds only the phrase 'across configurations', which reinforces scope but adds no row-range or format detail beyond structured data.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get) and resource (MCE operands and values across configurations), which is clear enough for an agent to know this is a read of multi-configuration editor data. It does not distinguish itself from close siblings like zemax_mce_summary or zemax_get_configuration, so it falls short of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no mention of prerequisites (e.g. an open file with configurations defined), and no routing to alternatives such as zemax_mce_summary or zemax_get_configuration. The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.