Skip to main content
Glama

Spatial 3D Display Oracle (Cloudflare Workers MCP)

spatial_list_quirks

Query Spatial 3D display and AR glasses quirk profiles (XREAL, VITURE, Rokid, RayNeo, Odyssey 3D). Free tier.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spatial_list_quirks"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
quirk_idNo
vendor_hexNo
product_hexNo

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?

No annotations are provided, so the description carries the full burden. 'Query' implies a read-only lookup and 'Free tier' usefully discloses a commercial/rate constraint, which is real behavioral value. However, it says nothing about result shape, pagination, or whether a single call returns all matching profiles — meaningful gaps for an unannotated 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?

Two short sentences, front-loaded with the resource and scope, with no filler. The trailing 'Free tier.' is terse to the point of ambiguity but is at least placed last so it does not obstruct the main purpose statement.

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?

For a four-parameter tool with no annotations, no output schema, and no parameter documentation, a single-sentence description leaves too much unspecified — particularly identifier formats and filter combination behavior. An agent could guess a call, but not confidently or correctly on the first try.

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?

With 0% schema description coverage, all four parameters are undocumented. The description's vendor list loosely hints that vendor_hex relates to a vendor, but it never explains that vendor_hex/product_hex are hex identifiers or what format they take, and it does not disambiguate the free-text query from the exact-match quirk_id. The schema gap is not compensated.

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 gives a specific verb ('Query') and a concrete resource ('Spatial 3D display and AR glasses quirk profiles') and even enumerates the covered vendors (XREAL, VITURE, Rokid, RayNeo, Odyssey 3D), which tells an agent exactly what domain this tool serves. It stops short of explicitly distinguishing itself from the EDID/optics/link-budget siblings, but the resource is clearly distinct from theirs.

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 use this tool versus spatial_edid_inspect or the other siblings, and no guidance on how to choose between the query, quirk_id, vendor_hex and product_hex parameters — e.g. whether they are ANDed or mutually exclusive. The only usage-adjacent information is the 'Free tier' note, which hints at access limits but not selection criteria.

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.