Skip to main content
Glama
Sign In

Commonlands Optics: M12 Lens and C-Mount Lens Finder + Field-of-View Calculator

by com.commonlands
OverviewDiscussionsAdmin

Resolve a live lens product

resolve_lens_product
Read-onlyIdempotent

Resolve a lens family or exact full SKU to current published Shopify variants. A family requires explicit variant selection; no fixture specifications or inferred configuration. Use the optical part number with calculate_field_of_view for sensor-specific optics.

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": {
      "sku": "<sku>"
    },
    "name": "resolve_lens_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description contributes behavioral context the annotations don't: resolution is against the live published catalog and the tool refuses to infer configuration for a family. It still omits failure behavior (unknown SKU, unpublished product) and what the response contains.

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?

Three sentences, front-loaded with the resolution contract, with no filler. The negative constraint ('no fixture specifications or inferred configuration') is terse and somewhat jargon-heavy but earns its place by preventing a common misuse.

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?

For a one-parameter lookup with no output schema, the definition covers input shape and the main constraint, but it never says what comes back for a family versus an exact SKU, nor what happens when nothing matches. An agent can call it correctly but cannot predict the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry the meaning of 'sku', and it does: the single parameter accepts either a lens family identifier or an exact full SKU. It does not specify format conventions or ambiguity resolution when a family name is supplied, which keeps it below 5.

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?

States a specific verb ('Resolve'), a specific resource ('lens family or exact full SKU'), and a specific target ('current published Shopify variants'). The family-vs-exact-SKU distinction makes it clearly different from search_lens_catalog or read_shopify_products without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real routing guidance: family input 'requires explicit variant selection' and the tool will not honor fixture specifications or inferred configuration, which tells the agent when this tool is the wrong choice. It also points to the companion call for sensor-specific optics ('use the optical part number with calculate_field_of_view'). No explicit when-to-use contrast against search_lens_catalog, hence not a 5.

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

All Commonlands Optics: M12 Lens and C-Mount Lens Finder + Field-of-View Calculator toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources