Skip to main content
Glama
Sign In
evanatpizzarobot

vr-org-mcp

by evanatpizzarobot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search VR / AR / XR news

search_vr_news
Read-only

Find VR, AR, and XR headlines from VR.org's live feed and originals, newest first. Filter by category or keywords to locate relevant news quickly.

Instructions

Returns the latest VR, AR, and XR headlines from VR.org's live aggregated feed plus VR.org originals, newest first. Optionally filter by category and by keywords: every keyword must appear in the headline, snippet, tags or source, in any order, and headline matches are listed first. Use a few keywords ('steam frame price') rather than a sentence, and omit the query for the latest headlines.

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-50 (default 20).
queryNoOptional keywords, e.g. 'steam frame price'. All must match, in any order. Omit for the latest headlines.
categoryNoOptional category filter: hardware, gaming, software, enterprise, ar, or xr. Omit for all categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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
    • changedInput schema / properties / query / description
      Previous value: -"Optional keyword to match in the title or snippet."New value: +"Optional keywords, e.g. 'steam frame price'. All must match, in any order. Omit for the latest headlines."
  2. Changed2 schema fields changedv0.1.3
    • addedInput schema / properties / category / maxLength
      Added value: +100
    • addedInput schema / properties / query / maxLength
      Added value: +500
  3. First observedv0.1.2

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds real behavioral detail beyond them: every keyword must match across headline/snippet/tags/source, matching is order-independent, and headline matches are ranked first. It adds value without contradicting the annotations.

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?

Three sentences, each earning its place: source and ordering first, then match semantics, then a practical query-writing tip. Front-loaded with the most decision-relevant information and free of filler.

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?

With only three optional parameters, no output schema, and full schema coverage, the description supplies everything needed to call the tool correctly: what it returns, ordering, filter semantics, and how to shape the query. Nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining where keywords are matched (headline, snippet, tags, source) and the ranking rule that headline matches come first. It also reinforces the 'omit for latest' behavior of the query parameter.

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 and resource ('Returns the latest VR, AR, and XR headlines'), names the source ('VR.org's live aggregated feed plus VR.org originals'), and specifies ordering ('newest first'). This clearly separates it from siblings like get_vr_article and list_vr_originals.

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

Usage Guidelines4/5

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

Gives concrete usage guidance: use a few keywords rather than a sentence, and omit the query for the latest headlines — an explicit when/when-not. It doesn't name a sibling alternative or state exclusions relative to other news-ish tools, so it stops short of a 5.

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