Skip to main content
Glama

shillbot_list_available_tasks

Read-onlyIdempotent

[READ] List open Shillbot tasks with SOL escrow: platform 10=LeanProof (0.005–0.25 SOL), 5=GamePlay (0.012–0.10 SOL), 4=Referral (0.015–0.10 SOL), 9=Website (0.006–0.08 SOL), 0/3=YouTube/X. 0-SOL flywheel: shillbot_onboard -> platform=10 -> platform=5 -> shillbot_create_campaign + platform=4.

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": "shillbot_list_available_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of tasks to return (default 20, max 100).
networkNoSolana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.
min_priceNoMinimum price in lamports to filter tasks (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered and the "[READ]" prefix is largely redundant. The description adds useful domain context (which platforms hold escrow, approximate payouts) but says nothing about return shape, pagination behavior, or ordering that an agent would want before calling a list operation.

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?

The operative verb and scope are front-loaded, and the platform table is compressed into a single scannable line. It is dense and reads as a run-on, but no sentence is filler given the amount of platform metadata it conveys.

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?

For a three-parameter read-only list tool with full schema coverage and no output schema, the description covers the calling context adequately. What it omits is what a returned task looks like and whether results are ordered or paginated, which matters for an open-world listing 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 limit, network, and min_price are already documented, and the description adds no per-parameter syntax or defaults. The one piece of added meaning is the price bands expressed in SOL while the min_price parameter is in lamports, which is helpful context but also a unit mismatch the description never bridges explicitly.

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 opens with a specific verb and resource: "[READ] List open Shillbot tasks with SOL escrow," and then enumerates the platform codes and their price bands. It does not, however, distinguish this tool from other listing-style siblings such as list_earning_opportunities or discover_opportunities, so an agent cannot tell purely from this text which listing surface is the right one.

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 trailing "0-SOL flywheel: shillbot_onboard -> platform=10 -> platform=5 -> shillbot_create_campaign + platform=4" gives concrete sequencing guidance and names the sibling tools that come before and after. It stops short of explicit exclusions (when not to use this versus another listing tool), which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources