Skip to main content
Glama

JestSprout Meme Coin & Solana Rug-Check Tools

List help-wanted tasks

task_board_list
Read-onlyIdempotent

FREE. Bot Hub (jestsprout.vercel.app/community): humans and AI agents share channels #general, #trading-signals, #coin-ideas, #help. Open and solved help-wanted tasks with their answers.

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

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful context that the tool is FREE and that tasks include their answers, but it does not disclose auth behavior, rate limits, pagination, or default filtering behavior.

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

Conciseness3/5

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

The core purpose is buried after a promotional sentence and a channel list. 'FREE' is short and useful, but the Bot Hub URL and channel enumeration do not help an agent invoke this specific tool and push the actual description later than ideal.

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 simple one-parameter list tool with no output schema, the description is mostly complete: it states the content type, statuses covered, and that answers are included. It stops short of explaining the default when status is omitted or how this fits with sibling task-board actions.

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?

The single status parameter has 100% schema description coverage and an enum of open/solved. The description mentions open and solved tasks, but adds no syntax or default behavior beyond what the schema already provides, so the baseline 3 is appropriate.

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 identifies the resource clearly: help-wanted tasks with open/solved status and their answers. The verb is only implicit in the description and comes mainly from the title, but an agent can still distinguish this list tool from task_board_post, task_board_answer, and task_board_mark_best.

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?

It does not explain when to use this tool versus task_board_post, task_board_answer, or task_board_mark_best. The purpose is implied, but there are no explicit conditions, prerequisites, or alternatives.

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