Skip to main content
Glama
Sign In

XGR MCP Gateway

by io.github.xgr-network
OverviewDiscussionsAdmin

Cancel XDaLa session start handoff

cancel_xdala_session_start_handoff
Idempotent

Cancel pending xDaLa session start handoff metadata only. This preparation/read-only MCP tool does not sign, submit, execute, or cancel on-chain work.

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": {
      "handle": "<handle>"
    },
    "name": "cancel_xdala_session_start_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesOpaque handoff handle returned by a previous XDaLa MCP tool.

Output Schema

NameRequiredDescriptionDefault
dataYesStructured result data returned by the XGR MCP gateway.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior1/5

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

The description claims this is a 'preparation/read-only MCP tool', but the annotations set readOnlyHint=false, indicating it is not read-only. This is a direct contradiction. Additionally, while it says it does not sign/submit/execute/cancel on-chain work, the tool name suggests cancellation of metadata, which is a write operation.

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?

The description is concise: two sentences that convey purpose and behavioral constraints without any redundant or extraneous information.

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?

Given the tool has one parameter, an output schema, and annotations, the description is relatively complete. However, the contradiction between description and annotations on read-only nature reduces clarity and completeness. It does not explain what cancelling metadata means or what happens to the session.

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 a detailed description for the 'handle' parameter. The description adds no further semantics beyond the schema, so baseline 3 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 cancels pending xDaLa session start handoff metadata. It distinguishes itself from sibling tools like cancel_operation_handoff and cancel_xdala_bundle_deploy_handoff by specifying 'metadata only' and that it does not perform on-chain work.

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?

The description implies the tool is for canceling a pending handoff, and the name clarifies the specific handoff type. It does not explicitly state when to use vs alternatives, but the context is clear. Adding prerequisites like needing a handle would improve.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XGR MCP Gateway toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources