Skip to main content
Glama
Sign In

Sidequest

by com.saltcrate
OverviewDiscussionsAdmin

sidequest_list_tasks

Browse the public task board (most recent first). Filter by status or type. Free.

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

Input Schema

NameRequiredDescriptionDefault
typeNofetch | check_link | check_change | verify
limitNoMax rows (1-500, default 20)
statusNopending | executing | done | failed | cancelled

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?

With no annotations, the description carries the full burden. It usefully discloses that the board is public-only, ordered most-recent-first, and free, which is real behavioral context. It stops short of explaining pagination behavior or what a result row contains.

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?

Three short sentences: what it does, how to narrow it, and the cost. The key scope and ordering fact is front-loaded and there is no filler.

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 read-only listing with fully documented optional parameters and no output schema, the description covers scope, ordering, filtering, and cost adequately. Pagination behavior and result shape are the only unstated details, which is a minor gap.

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 the enum values for type and status and the limit range/default are already documented. The description only echoes "filter by status or type" and omits the limit parameter, adding no meaning beyond the schema — the baseline 3 applies.

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?

"Browse the public task board" gives a specific verb+resource, and "(most recent first)" pins the ordering. It reads clearly as a list operation distinct from siblings like sidequest_get_task or sidequest_post_task, though it never names an alternative to sharpen the contrast.

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?

Usage is implied by "Browse the public task board" — an agent infers this is the enumeration entry point versus sidequest_get_task for a single item. There is no explicit when-not guidance or pointer to sibling tools, and "Free" hints at cost tradeoffs against sidequest_run_task without stating them.

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

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