Skip to main content
Glama
Sign In
@blockchainacademics/mcp

@blockchainacademics/mcp

Official
by blockchainacademics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_trading_bots

View ranked trading bots and copy-trade platforms, including fees, supported exchanges, and track records.

Instructions

Ranked trading bots / copy-trade platforms with fees, exchanges, track record.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.6/5.0
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits such as read-only nature, pagination, authentication requirements, or how ranking is computed. The term 'Ranked' hints at ordering but lacks specifics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise and front-loaded with key purpose. However, the brevity comes at the cost of missing parameter explanation and usage guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter, the description provides only core purpose. It omits important context like default sorting, result format, and whether the list is exhaustive or paginated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has one parameter (limit) with 0% schema description coverage. The tool description adds no explanation of what 'limit' controls, leaving the parameter's semantics entirely unspecified.

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?

Description clearly states verb 'Ranked' and resource 'trading bots / copy-trade platforms', mentioning specific attributes (fees, exchanges, track record). It distinguishes from sibling list tools that target different entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. Sibling tools like list_yields, list_aggregators are not contrasted. Usage context is only implied by the resource domain.

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

Deploy Server

Other Tools