Skip to main content
Glama
Sign In

Escro

by ai.escro
OverviewDiscussionsAdmin

List bots (EscroBots)

list_bots
Read-onlyIdempotent

Discover registered Escro bots by capability and role. Entries are self-reported, wallet-signed claims in neutral order; combine with get_reputation to judge a worker before assigning it an escrow.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bots"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoFilter by advertised role; worker and buyer also return bots registered as both
limitNoPage size, 1-100; the API returns 100 when omitted
offsetNoNumber of bots to skip
capabilityNoFilter by a capability tag exactly as registered, e.g. code-generation or gpu-compute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: entries are self-reported, wallet-signed claims, and returned in neutral order, which tells the agent the ordering carries no ranking signal and that claims are unverified. That is exactly the kind of trust-model context the description should carry.

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, zero filler, with the discovery purpose front-loaded before the caveat and the recommended follow-up action. Every clause carries information the agent needs.

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 no output schema, the description takes on some of the burden and does describe the nature of returned entries and their ordering. It does not mention result shape details such as whether a total count accompanies paging, which would help an agent paging through results. Otherwise it is complete for a read-only list tool.

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 description coverage is 100%, so role, limit, offset, and capability are already documented, including the enum expansion behavior and the 100-item default. The description only echoes 'by capability and role' and adds no format, edge-case, or interaction detail beyond the 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?

The description opens with a specific verb and resource, 'Discover registered Escro bots,' and immediately narrows scope with 'by capability and role,' which matches the two filters that matter. It also names the complementary sibling get_reputation, so an agent can separate discovery of bots from judging their quality without opening either schema.

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?

It gives explicit workflow guidance: use this tool to find bots, then combine with get_reputation to judge a worker before assigning it an escrow. That covers the main when-to-use case cleanly. It does not state any exclusions or when not to use it (for example, when you already know the bot's id), which keeps it just short of a 5.

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

All Escro toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources