Skip to main content
Glama

XDaLa Workflow Builder

by io.github.xgr-network

Get XDaLa payload term statistics

get_xdala_payload_term_stats
Read-onlyIdempotent

Use this when the user asks for payload terms, payload words, payload Begriff statistics, or a statistic over all payload terms in a time range. For “last 14 days”, pass windowHours=336. Do not sample sessions for this task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoValue for the mode parameter.
limitNoMaximum number of records to return.
ownerNoEVM address of the XDaLa session owner or relevant account.
sourceNoSource type for deriving the prepared XDaLa request.
outcomeNoValue for the outcome parameter.
windowHoursNoValue for the window hours parameter.
minTermLengthNoValue for the min term length parameter.

Output Schema

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

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds value by stating 'Do not sample sessions' (behavioral trait) and the windowHours hint, which is not in annotations. No contradiction.

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 two sentences: first sentence defines when to use, second provides a usage example and constraint. No wasted words, front-loaded with critical information.

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 7 optional parameters, 100% schema coverage, and existing output schema, the description provides a key usage example and a constraint. It does not explain all parameters, but the schema covers them. The description is sufficient for the agent to invoke the tool correctly.

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?

Schema coverage is 100%, so baseline 3. The description adds specific parameter guidance ('For “last 14 days”, pass windowHours=336'), which helps the agent understand the time range parameter better than the schema alone.

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 explicitly states the tool is for 'payload terms, payload words, payload Begriff statistics, or a statistic over all payload terms in a time range.' It clearly distinguishes from siblings like get_xdala_payload_field_value_stats and get_xdala_payload_key_stats by focusing on 'terms' and specifying 'all payload terms'.

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 tells when to use ('when the user asks for ...') and provides a concrete example ('For “last 14 days”, pass windowHours=336') and a constraint ('Do not sample sessions for this task'). It does not explicitly mention alternatives, but the context and sibling list imply when not to use.

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