Skip to main content
Glama

XDaLa Workflow Builder

by io.github.xgr-network

Get XDaLa session receipt logs

get_session_receipt_logs
Read-onlyIdempotent

Use this to inspect what an XDaLa session actually did. Returns decoded engine receipt data such as input payload, API saves, contract saves, execution contract, rule contract, valid flag, inner gas usage and optional raw receipt logs. Do not use this for a simple transaction timeline; use get_session_transactions instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records to return.
ownerYesEVM address of the XDaLa session owner or relevant account.
filtersNoValue for the filters parameter.
stepIdsNoValue for the step ids parameter.
includeTxNoValue for the include tx parameter.
sessionIdYesXDaLa session identifier used to query runtime or explorer data.
includeRawNoValue for the include raw parameter.
includeBlockNoValue for the include block parameter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesStructured result data returned by the XGR MCP gateway.

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds detail on returned data but does not disclose additional behavioral constraints (e.g., pagination, performance). No contradictions with annotations.

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 sentences, no redundant wording, front-loaded with action and key details.

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 output schema exists, description is sufficient: covers use case, return data types, and sibling distinction. Slightly lacking details on optional parameters beyond schema, but adequate for 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?

Input schema covers all 8 parameters with descriptions (100% coverage). Description does not add semantic value beyond the schema; it only indirectly refers to 'optional raw receipt logs' which corresponds to includeRaw. 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?

Description uses specific verb 'inspect' and resource 'XDaLa session receipt logs', lists example output fields, and explicitly distinguishes from sibling 'get_session_transactions'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly states when to use (inspect session actions) and when not to use (simple timeline) with direct alternative named ('use get_session_transactions instead').

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

All XDaLa Workflow Builder toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation2/5

There are many overlapping session-listing tools (list_xdala_sessions, get_recent_xdala_sessions, find_latest_xdala_session, list_xdala_session_ids, get_latest_session_payload) and duplicate validation tools (validate_xdala_bundle is an alias for validate_xgr_multibundle). Descriptions help but boundaries are still unclear.

Naming Consistency4/5

The verb_noun snake_case pattern is consistent across nearly all tools (get_, list_, create_, cancel_, validate_). Minor inconsistencies include the alias validate_xdala_bundle and interchangeable verbs like get_ vs read_ vs resolve_ for similar read operations.

Tool Count1/5

With 95 tools, this is far beyond the 25+ threshold for 'too many'. While the domain is broad, the sheer number makes the tool surface unwieldy and difficult for an agent to navigate.

Completeness4/5

The tool set covers a wide range of operations: handoffs, session queries, transaction exploration, contract reads, validation, gas requests, and purchases. Minor gaps exist (e.g., no direct workflow editing tools), but overall the surface is remarkably complete.

Resources