Skip to main content
Glama
Sign In
roblox-devproducts-mcp

roblox-devproducts-mcp

by frrazer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_game_pass

Retrieve complete details for a specific game pass using its ID and universe ID.

Instructions

Get the full details of a single game pass by its ID within a universe.

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": {
      "universeId": "<universeId>",
      "gamePassId": "<gamePassId>"
    },
    "name": "get_game_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
gamePassIdYesThe game pass ID.
universeIdYesThe Roblox universe (game) ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

The description indicates a read-only operation via the word 'Get', which implies no side effects. Without any annotations, this sufficiently signals non-destructive behavior. However, it does not detail authentication needs, rate limits, or response structure, though for a simple retrieval this is adequate.

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?

A single sentence of 16 words, front-loaded with the verb and resource, and no extraneous information. Every word earns its place.

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

Completeness4/5

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

Given the tool's simplicity (2 required string params, no output schema, no nested objects), the description is complete enough to understand its purpose and usage. It does not describe the return value, but for a straightforward get operation, this is acceptable.

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%, with each parameter described in the schema. The description adds no additional meaning beyond the schema (e.g., 'by its ID within a universe' mirrors the params). Baseline 3 is appropriate as the schema already carries the full burden.

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?

The description uses a specific verb ('Get'), a clear resource ('game pass'), and a scope ('by its ID within a universe'). It distinctly identifies the action and resource, differentiating from sibling tools like 'list_game_passes' (which lists all) or 'create_game_pass' (which creates).

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 usage when retrieving details of a single known game pass, but provides no explicit guidance on when to use this tool versus alternatives such as 'list_game_passes', nor any exclusions or prerequisites. Usage is implied but not directly stated.

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