Skip to main content
Glama

XDaLa Workflow Builder

by io.github.xgr-network

Find reusable XRC-137 rules

find_reusable_xrc137_rules
Read-onlyIdempotent

Read-only metadata-assisted search for existing owner XRC-137 contracts that could be reused instead of redeployed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of records to return.
ownerYesEVM address of the XDaLa session owner or relevant account.
ruleHashNoValue for the rule hash parameter.
draftRuleNoValue for the draft rule parameter.
includeUsageNoValue for the include usage parameter.
allowEncryptedNoValue for the allow encrypted parameter.
requiredInputKeysNoValue for the required input keys parameter.
requiredOutputKeysNoValue for the required output keys parameter.

Output Schema

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

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already provide strong behavioral hints (readOnlyHint, openWorldHint, idempotentHint). The description adds 'metadata-assisted search' and 'reuse' context, reinforcing read-only behavior. No contradictions. The description complements the annotations adequately.

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 a single, well-structured sentence that front-loads the key purpose. No unnecessary words or repetition. Every part contributes meaning.

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 complexity (8 parameters, nested object) and the presence of a similar sibling ('get_unused_xrc137_rules'), the description could be more specific about the relationship with that sibling and what 'metadata-assisted' entails. However, the output schema exists and annotations are rich, so the description is minimally adequate but not comprehensive.

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%, so the baseline is 3. The description uses 'metadata-assisted' to hint at filtering, but does not add significant meaning beyond the schema's parameter descriptions. It does not explain how parameters combine or prioritize them, so marginal value is added.

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 uses a specific verb ('find'), identifies the resource ('reusable XRC-137 rules'), and specifies the context ('existing owner XRC-137 contracts that could be reused instead of redeployed'). It clearly distinguishes from siblings like 'get_unused_xrc137_rules' by emphasizing search and reuse.

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 when to use this tool: to find existing rules and avoid redeployment. However, it does not explicitly state when not to use it or compare it to the closely related sibling 'get_unused_xrc137_rules'. The context is clear but lacks explicit exclusions.

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