Skip to main content
Glama

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

by com.commonlands

Get product page details

get_product_page_details
Read-onlyIdempotent

Return fixture-backed product-page handoff details for one lens, including DynamoDB-sourced optical specs and gated datasheet policy. Product-page/catalog optical fields are not a substitute for sensor-specific FoV; call calculate_field_of_view for the lens/sensor pair. FoV rule: never estimate sensor-specific FoV from catalog fields; use calculate_field_of_view or match_lens_to_sensor. Use read_shopify_products for live product URL, price, availability, variant IDs, and metafields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuYesCommonlands short part number, for example CIL250.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds 'fixture-backed' (not live) and 'gated datasheet policy' (access restrictions). Warns about FoV limitation, which is useful behavioral context beyond annotations.

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?

Very concise: two core sentences plus a one-sentence FoV rule. Every sentence adds value. Front-loaded with main purpose. No fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With full schema coverage, annotations, and no output schema, the description covers purpose, usage context, and behavioral caveats. Slightly ambiguous what 'handoff details' precisely includes, but overall complete for agent decision-making.

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

Parameters3/5

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

Schema coverage is 100% with clear description of sku parameter (format and example). Description does not add parameter-specific meaning, which is acceptable since the schema already provides sufficient detail. Baseline 3.

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?

Clearly states the tool returns fixture-backed product-page handoff details for one lens, including specific content (optical specs, gated datasheet policy). Distinguishes from siblings like calculate_field_of_view and read_shopify_products.

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

Usage Guidelines5/5

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

Explicitly tells when to use alternatives: calculate_field_of_view for sensor-specific FoV, read_shopify_products for live data. Provides a negative rule ('never estimate sensor-specific FoV') and directs to specific sibling tools.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

Several tools have significant overlap in purpose and trigger keywords. calculate_field_of_view, match_lens_to_sensor, and get_lens_distortion_profile all share nearly identical use-case descriptions for FOV/sensor requests, while search_catalog, search_lens_catalog, and lookup_catalog all provide search/lookup functionality with subtle differences that are easy to confuse.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., calculate_field_of_view, create_cart, get_product, read_shopify_products, submit_rfq). No mixing of styles or unpredictable naming conventions.

Tool Count3/5

With 21 tools, the surface is noticeably heavy for a lens finder and FOV calculator, especially when several tools serve status/config purposes (get_catalog_snapshot_status, get_shopify_readonly_config_status, get_shopify_ucp_readiness). It sits in the 'feels heavy' range from the rubric.

Completeness4/5

The tool set covers the full lifecycle: catalog search, product details, sensor specs, FOV calculation, lens matching, distortion profiles, Shopify carts, purchase handoff, and RFQ submission. Minor gaps exist (e.g., no delete_cart or bulk sensor listing), but core workflows are well-supported.

Resources