Skip to main content
Glama

Spatial 3D Display Oracle (Cloudflare Workers MCP)

spatial_edid_inspect

Decode base64 or hex EDID 1.4, CTA-861, and DisplayID 2.0/2.1 binaries, verify checksums, and match quirks. 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": {
      "edid": "<edid>"
    },
    "name": "spatial_edid_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
edidYesBase64 or hex-encoded EDID binary (>=128B, multiple of 128B).
strict_checksumNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description must carry the full behavioral burden. It does disclose meaningful context that structured fields lack: supported standards, that checksums are verified, that quirks are matched, and that the call is metered at $0.005 (or covered by Polar Pro). It does not state error behavior for malformed or wrong-length input, nor that the operation is non-destructive/read-only, which are noticeable gaps for a zero-annotation tool.

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?

A single, densely packed sentence: capability scope first, then the pricing note. Every clause carries information and nothing is repeated from the schema. Slightly terse on the 'match quirks' clause, but no wasted words.

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 two-parameter decode tool with no output schema and no annotations, the description covers what is decoded and that it costs money, which is adequate. It leaves the agent guessing about return shape (parsed fields vs. report), failure modes on invalid binaries, and the effect of strict_checksum.

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 50%: the 'edid' parameter is documented in-schema, but 'strict_checksum' has no description. The mention of 'verify checksums' loosely connects to that parameter, but the description never explains what strict mode changes (fail vs. warn). Marginal compensation for the coverage gap – baseline 3.

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 specific verbs and resources: decode EDID 1.4 / CTA-861 / DisplayID 2.0/2.1 binaries, verify checksums, and match quirks. That is enough to distinguish it from spatial_edid_patch (which implies modification) and spatial_list_quirks, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the verbs 'decode' and 'verify' – an agent can infer this is the inspection entry point before patching. There is no explicit when-to-use/when-not-to-use statement, no prerequisite guidance, and no reference to the alternative tools in the family.

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.