Skip to main content
Glama
Sign In
evanatpizzarobot

vr-org-mcp

by evanatpizzarobot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Compare two VR headsets

compare_vr_headsets
Read-only

Compares two VR headsets side-by-side by partial or full name, returning prices, badges, descriptions, and retailer links from VR.org's catalog.

Instructions

Returns a side-by-side of two headsets (price, badge, description, retailer links) drawn from VR.org's curated catalog. Accepts partial names like 'Quest 3' or 'PSVR2'.

Input Schema

NameRequiredDescriptionDefault
aYesFirst headset name (partial match allowed).
bYesSecond headset name (partial match allowed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv0.1.3
    • addedInput schema / properties / a / maxLength
      Added value: +200
    • addedInput schema / properties / b / maxLength
      Added value: +200
  3. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the comparison is drawn from a curated catalog and returns specific field groups, which matters because no output schema exists.

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?

Two sentences, no filler. The returned-value summary is front-loaded and the partial-name affordance trails it as supporting detail.

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

Completeness5/5

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

For a two-parameter, read-only comparison tool with no output schema, the description covers what is compared, what comes back, and where the data comes from. Nothing an agent needs in order to call it correctly is missing.

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% and both parameters already document 'partial match allowed' with maxLength constraints. The description's example strings ('Quest 3', 'PSVR2') and the partial-match restatement add marginal illustration but no syntax or format detail beyond the schema, so the baseline 3 holds.

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?

States a specific verb+resource (side-by-side comparison of two headsets) and names the exact fields returned (price, badge, description, retailer links) plus the data source (VR.org curated catalog). This is clearly distinguishable from every sibling, all of which are single-item get/list/search tools.

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?

The description implies the use case (compare two named headsets) and usefully notes that partial names are accepted, so an agent knows it need not resolve exact titles first. However, it never states when to prefer this over a plain lookup or what happens when a name is ambiguous or missing.

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

Deploy Server

Other Tools