Skip to main content
Glama

XDaLa Workflow Builder

by io.github.xgr-network

List indexed XRC contracts

list_xrc_contracts
Read-onlyIdempotent

Read-only list of indexed XRC-137/XRC-729 contracts globally or filtered by owner/type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page number for paginated explorer/API results.
typeNoOperation or handoff type identifier.
limitNoMaximum number of records to return.
ownerNoEVM address of the XDaLa session owner or relevant account.

Output Schema

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

TDQS

A3.8/5.0
Behavior3/5

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

Description states 'Read-only list', matching annotations (readOnlyHint, idempotentHint, destructiveHint false). Adds context about global vs filtered listing, but no additional behavioral traits like pagination behavior or data freshness. Annotations already cover safety profile.

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, front-loaded with 'Read-only list', no wasted words. Highly concise and efficient.

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?

With output schema and full annotation coverage, description adequately explains scope and filtering. Could mention pagination (page, limit) but not necessary given schema. Complete for purpose.

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%, parameters well-documented. Description adds 'globally or filtered by owner/type', mapping to owner and type params, but doesn't enhance beyond schema. Baseline 3 applies.

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 clearly states it lists indexed XRC-137/XRC-729 contracts, globally or filtered. Verb 'list' specifies action, 'XRC contracts' the resource, and 'globally or filtered by owner/type' distinguishes from sibling tools like list_xrc729_contracts_by_executor or get_xrc_contract.

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?

Implies use for listing indexed contracts with optional filters, but no explicit when-not-to-use or alternatives. Context signals suggest many sibling tools, but description lacks guidance on choosing this vs others.

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