Skip to main content
Glama

shillbot_list_pending_approval

Read-onlyIdempotent

[READ] (CLIENT-SIDE) List Shillbot tasks awaiting your client review across all campaigns. Approve acceptable work with shillbot_approve_task. Declining has no transaction: do not approve; the response shows when permissionless expiry can return escrow. Requires the campaign client wallet.

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

Input Schema

NameRequiredDescriptionDefault
networkNoSolana network: "mainnet" (default) or "devnet". Mismatched network = the on-chain accounts won't be found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Even though annotations already declare readOnlyHint=true and idempotentHint=true, the description adds meaningful context: it is client-side, requires the campaign client wallet, and explains that the response shows when permissionless expiry can return escrow. This is exactly the kind of non-obvious behavior that helps an agent invoke the tool safely.

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 description is compact and front-loaded with '[READ] (CLIENT-SIDE)' and the core purpose. Each sentence adds distinct value: purpose, approval workflow, decline behavior, and a required precondition. There is no filler or redundancy.

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

Completeness5/5

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

For a simple one-parameter read-only tool, the description covers purpose, scope, required wallet context, related actions, and important escrow behavior. The lack of an output schema is compensated by explicitly describing what the response reveals about permissionless expiry.

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 optional 'network' parameter is fully documented in the schema with a clear explanation and a mismatch caveat. Since schema description coverage is 100%, the description does not need to repeat parameter details and adds no additional parameter-level meaning. Baseline 3 is appropriate.

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 uses a specific verb and resource: 'List Shillbot tasks awaiting your client review across all campaigns.' It clearly distinguishes this from the sibling shillbot_approve_task and from a generic task listing by emphasizing the pending-client-approval state.

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

Usage Guidelines5/5

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

It explicitly tells the agent what to do next for acceptable work ('Approve acceptable work with shillbot_approve_task') and what not to do when declining ('do not approve'). It also provides the workflow context that declining has no transaction, which helps the agent decide between this read and subsequent approval actions.

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