Skip to main content
Glama

get_tasks

Live task board: instant/micro tasks paying ledger credit (no approval), plus cash bounties. Start here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose real domain behavior: instant tasks pay ledger credit with no approval, and cash bounties form a separate class. That 'no approval' detail is meaningfully behavioral. It says nothing about whether the call is read-only, result size, pagination, or freshness of the 'live' board.

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?

Two compact fragments, front-loaded with the resource and immediately followed by the routing cue 'Start here' — nothing is wasted. It leans toward telegraphese, with undefined jargon like 'ledger credit' that a newcomer cannot resolve from this text alone.

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 zero-parameter tool with no output schema and no annotations, the description should sketch what comes back; it only names task categories and payment types without any indication of result shape, volume, or ordering. It is enough to decide to call it, but thin for interpreting the response.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No misleading parameter hints are given.

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 names the resource (a live task board) and its contents precisely — instant/micro tasks paying ledger credit plus cash bounties — which lets an agent distinguish this from siblings like get_draws or get_mission. It lacks an explicit verb (e.g. 'list' or 'fetch'), so the action is implied by 'board' rather than stated, keeping it just below a 5.

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?

'Start here' is a genuine workflow hint that positions this as the entry point among the listed siblings, which is useful orientation. However, there is no explicit statement of when not to use it, no named alternative for filtered or detailed lookups, and no prerequisites described.

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.