Skip to main content
Glama

Spatial 3D Display Oracle (Cloudflare Workers MCP)

spatial_link_budget

Solve VESA CVT-RB2 timing and check HDMI 1.4/2.0/2.1 FRL, DP 1.2/1.4/2.1 UHBR, and USB-C bandwidth with DSC 1.2 8bpp floor. Free tier.

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": {
      "width": "<width>",
      "height": "<height>",
      "refresh_hz": "<refresh_hz>"
    },
    "name": "spatial_link_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
bpcNo
dscNo
linkNo
ntscNo
widthYes
chromaNo
heightYes
precisionNo
refresh_hzYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavioral facts: which timing standard is solved (CVT-RB2), that DSC 1.2 with an 8bpp floor is applied, and which interfaces are checked. It says nothing about the response shape, whether results are pass/fail or a computed budget, units, or any rate limits implied by 'Free tier', so significant gaps remain.

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?

Two tight sentences, front-loaded with the primary computation and followed by the supported interface matrix. 'Free tier.' is curt but earns its place as a pricing signal; no filler otherwise.

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 9-parameter computational tool with no output schema and no annotations, so the description should explain input semantics and what comes back. It covers the domain standards but leaves the majority of parameters and the entire result contract unexplained.

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 9 parameters, and the description compensates almost not at all. It implies that bpc and dsc relate to the 'DSC 1.2 8bpp floor' and that ntsc/chroma/precision affect timing, but never defines link, ntsc, precision, or the width/height/refresh ranges already bounded in the schema.

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 names two specific operations (solve VESA CVT-RB2 timing; check link bandwidth) and enumerates the concrete standards covered (HDMI 1.4/2.0/2.1 FRL, DP 1.2/1.4/2.1 UHBR, USB-C, DSC 1.2). This is a clear verb+resource statement that an agent can distinguish from the EDID and optics siblings, though it never explicitly says so.

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 guidance on when to choose this tool versus the EDID inspect/patch siblings, no stated prerequisites, and no exclusions. 'Free tier' hints at a paid counterpart but does not tell the agent when or why that matters.

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.