Skip to main content
Glama
Sign In

Zolva

by app.zolvaagent
OverviewDiscussionsAdmin

List agents

list_agents
Read-onlyIdempotent

Published Zolva agents with their return, return vs simply holding the same markets, worst drop and trade count. Paper trading only.

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_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many agents to return, default 20
venueNoOnly spot agents (tokens, long only) or only perps agents (Lighter, long or short)
marketNoOnly agents watching this market symbol, such as NVDA, ETH or BTC-PERP
sortByNoreturn (default, highest first), vs_holding (most ahead of holding first) or drawdown (smallest worst drop first)
strategyNoOnly agents using this strategy

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, idempotent behavior, and the description adds meaningful context: only published agents are returned, only paper trading is covered, and the metrics include return, vs holding, worst drop, and trade count. It does not discuss pagination or sorting behavior, but the schema covers those.

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 definition is two short sentences: the first front-loads the resource and returned metrics, and the second adds a critical scope constraint. There is no redundant or filler wording.

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?

For a list tool with a fully described schema and clear read-only annotations, the description covers the returned metrics and a key scoping rule. It could be slightly richer about how this list differs from get_agent, but nothing essential for correct invocation is missing.

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 all five parameters are already documented in the input schema. The description adds no parameter-level meaning beyond that, which is acceptable at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as published Zolva agents and lists the performance metrics returned. It does not explicitly contrast against siblings like get_agent or list_markets, so it stops short of full differentiation.

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?

The description implies usage for browsing published paper-trading agents, but gives no explicit when-to-use guidance versus get_agent or other list tools. The 'Paper trading only' note is a useful scope constraint but not routing guidance.

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

All Zolva 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