Skip to main content
Glama

Spatial 3D Display Oracle (Cloudflare Workers MCP)

spatial_lenticular_optics

Compute dynamic eye-tracked slanted-lenticular shader calibration uniforms for glasses-free 3D panels. Metered ($0.005/call or Polar Pro).

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": {
      "display_width_px": "<display_width_px>",
      "display_height_px": "<display_height_px>",
      "pitch_lpi": "<pitch_lpi>",
      "screen_width_inches": "<screen_width_inches>",
      "slant_slope": "<slant_slope>"
    },
    "name": "spatial_lenticular_optics"
  }
}

Input Schema

NameRequiredDescriptionDefault
eye_z_mmNo
pitch_lpiYes
slant_slopeYes
center_phaseNo
subpixel_orderNo
display_width_pxYes
eye_x_normalizedNo
display_height_pxYes
screen_width_inchesYes
nominal_viewing_distance_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses metered pricing and a Polar Pro option, but does not state whether the call is read-only, what happens on invalid inputs, what units are expected, or what the output represents.

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?

The description is two tightly written sentences with no filler, and the core purpose is front-loaded before the billing detail. Every sentence contributes information.

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?

This is a complex 10-parameter compute tool with no annotations and no output schema, yet the description is only two sentences. It omits nearly all parameter semantics, does not describe return values, and gives only minimal behavioral context.

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% across 10 parameters, and the description adds only vague domain hints such as 'eye-tracked' and 'slanted-lenticular'. It does not explain required versus optional fields, units, valid ranges, defaults, or the meaning of center_phase and subpixel_order.

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 uses a specific verb, 'Compute', and names the exact resource, 'dynamic eye-tracked slanted-lenticular shader calibration uniforms for glasses-free 3D panels'. This is clearly distinct from sibling tools such as spatial_edid_inspect or spatial_link_budget, so an agent can identify its role without opening the schema.

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?

The description identifies the domain but gives no explicit when-to-use guidance, no alternatives, and no prerequisites beyond a billing note. It implies use for glasses-free 3D panel calibration, but provides no routing logic or conditions that would help an agent choose it over another tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.