Skip to main content
Glama
Sign In
XenozMCP

XenozMCP

by Xenoz-GitHub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

screen_capture

Capture screenshots of the Roblox Studio viewport from the current scene. Supports single or multi-angle captures.

Instructions

Capture the Roblox Studio viewport. Takes a screenshot of the current scene.

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": "screen_capture"
  }
}

Input Schema

NameRequiredDescriptionDefault
singleNoIf true, capture a single angle instead of multi-angle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states tool captures a screenshot without any details about side effects, output format (file, clipboard, response), permissions needed, or limitations. Minimal behavioral disclosure.

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 concise sentences with no filler. Every word contributes to understanding the core action. Efficiently structured.

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?

Tool is simple with one optional parameter and no output schema. Description adequately covers what the tool does but omits what the tool returns (image data, file path, etc.). Lacks information that would help an agent understand how to use the captured screenshot.

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?

Input schema has 100% description coverage for the single parameter, explaining it controls single vs multi-angle capture. Description adds no additional value or context beyond what schema provides.

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?

Description clearly states tool captures Roblox Studio viewport/screenshot. Verb 'Capture' and resource 'Roblox Studio viewport' are specific and unambiguous. No sibling tools perform similar function, so differentiation is unnecessary.

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?

No explicit guidance on when to use this tool versus alternatives, or when to set the 'single' parameter. Usage is implied by the description, but no context about prerequisites or typical scenarios.

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