CODE V MCP

Overview Schema Source Related Servers Discussions Admin

open_lens

Open a .len lens file as a working copy to return its surfaces, materials, units, wavelengths, and fields for optical data review and editing in CODE V MCP.

Instructions

打开一个 .len 镜头文件的工作副本，并返回其表面、材料、单位、波长与视场。

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": {
      "path": "<path>"
    },
    "name": "open_lens"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes

Output Schema

Name	Required	Description	Default
`path`	No	File the working copy was opened from.
`title`	No
`units`	Yes
`fields`	No
`source`	Yes
`aperture`	No
`surfaces`	Yes
`warnings`	No
`raw_listing`	No	Verbatim surface listing the values were parsed from.
`wavelengths`	No
`stop_surface`	Yes
`zoom_position`	No
`aperture_usage`	No		unknown
`dimension_code`	Yes	Raw CODE V GetDimension value: 0 inch, 1 cm, 2 mm.
`zoom_positions`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Working copy' hints at session state, but it never says whether the underlying file is modified, whether the copy must later be released via close_session, whether repeated opens are allowed, or what permissions are needed. For a state-creating operation this is a significant gap.

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?

One compact sentence, front-loaded with the action and resource, followed by the returned data. No padding 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?

An output schema exists, so return values need not be re-explained, and the description correctly enumerates the returned categories. However, for a session-opening tool with no annotations and a documented sibling (close_session), the lifecycle and file-safety context an agent needs is absent.

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 single required 'path' parameter is never explained. The mention of a '.len 镜头文件' does implicitly signal the expected file type, which gives partial meaning, but format, absolute-vs-relative path, and error behavior are all unaddressed.

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 gives a specific verb ('打开' / open) and a specific resource (a working copy of a .len lens file), and lists what the call surfaces (surfaces, materials, units, wavelengths, fields). This distinguishes it reasonably from create_lens and get_lens, though it never explicitly names an alternative sibling. It is clear but lacks the explicit sibling differentiation that would earn a 5.

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?

There is no when-to-use guidance, no statement of when to prefer this over create_lens, get_lens, or open-a-new-session flows, and no mention of prerequisites or the close_session lifecycle. The agent is left to infer the correct moment to call it.

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

Deploy Server