Skip to main content
Glama
Sign In
XGR MCP Gateway

XGR MCP Gateway

Official
by xgr-network
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get XGR MultiBundle schema

get_xgr_multibundle_schema

Retrieve the canonical XGR MultiBundle schema for multi-bundle operations.

Instructions

Use this to retrieve the canonical XGR MultiBundle schema for xgr-multi-bundle@1.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the purpose but does not mention any side effects, read-only nature, authentication requirements, or return format. For a retrieval tool, it is implied to be read-only, but lack of explicit detail reduces transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence front-loading the purpose. It is efficient, though could provide a bit more context (e.g., what the schema contains) without becoming verbose.

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 zero parameters, no output schema, and no annotations, the description covers the essential purpose. However, it does not specify the return format or data type, which would be helpful given the completeness burden on the description.

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?

The input schema has zero parameters, so the baseline is 4. The description adds no param info because none exist, which is appropriate.

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 clearly states the tool retrieves the canonical XGR MultiBundle schema for a specific version ('xgr-multi-bundle@1'), using a specific verb and resource. It distinguishes from siblings like get_xgr_session_start_schema which retrieve different schemas.

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 through the phrase 'Use this to retrieve...' but does not explicitly state when to use this tool over alternatives, nor provides conditions or prerequisites. The sibling context provides implicit differentiation via tool names, but no explicit guidance is given.

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