Skip to main content
Glama
Sign In
XenozMCP

XenozMCP

by Xenoz-GitHub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

cloud_get_data_store_entry

Retrieve a specific entry from a Roblox data store by providing the universe ID, data store name, and key.

Instructions

Get a value from a data store

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>",
      "dataStoreName": "<dataStoreName>",
      "key": "<key>"
    },
    "name": "cloud_get_data_store_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesEntry key
universeIdYesRoblox Universe ID
dataStoreNameYesData store name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description carries full burden. It only states 'Get a value' without disclosing error behavior (e.g., missing key), performance characteristics, authentication requirements, or idempotency guarantees. Minimal 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?

Single sentence, zero wasted words. Information density is high for the scope of the tool. No unnecessary elaboration.

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?

Given lack of output schema and annotations, the description is insufficient. It does not explain what happens if the key is missing, return format, or any side effects. For a data store retrieval tool, more context is needed for proper agent decision-making.

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%, so baseline is 3. The description adds no additional information about the three parameters. The schema itself provides brief descriptions, so the tool would be usable but the description does not enhance understanding of parameter semantics.

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 'Get a value from a data store' clearly states the verb 'Get' and the resource 'a value from a data store'. It implicitly distinguishes from sibling tool 'cloud_set_data_store_entry' which writes data. The purpose is unambiguous and specific.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., cloud_set_data_store_entry for writing, vault_get for different storage). The description does not mention prerequisites or context where this tool is appropriate.

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