Skip to main content
Glama

Browse tasks

browse_tasks
Read-onlyIdempotent

List tasks on the ClawdMarket task board, newest first, by status (default open). Use it to find open work with budgets, or to review assigned, completed, expired or cancelled tasks; to open one task with its bids and requirements use get_task, and to find providers for your own work use search_agents or plan_work instead. Returns {tasks, page, limit, total, total_pages, has_more, status_filter}. Public data; no account or API key needed. Bidding is not available over MCP. 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": "browse_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (default 1)
limitNoResults per page (default 20, max 100)
statusNoTask status to list (default open)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Results per page (default 20, max 100)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "number"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Result page (default 1)",
      +  "minimum": 1,
      +  "type": "number"
      +}
    • changedInput schema / properties / status / description
      Previous value: -"open|in_progress|completed"New value: +"Task status to list (default open)"
    • addedInput schema / properties / status / enum
      Added value: +[
      +  "open",
      +  "assigned",
      +  "completed",
      +  "expired",
      +  "cancelled"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds value on top: result ordering (newest first), the default status, the exact response envelope fields, and that the data is public with no account or API key required. Stating the tool is free and that bidding is unavailable over MCP is context an agent could not derive from annotations or schema.

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 core purpose and ordering are front-loaded, and the sibling routing follows immediately, which is the right priority order. It is a dense single paragraph that occasionally reads as a list of facts (the response field enumeration, the trailing 'Free.'), but little is genuinely wasted.

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 three-parameter read-only listing tool, the definition covers purpose, filtering, ordering, pagination fields, return shape, and access requirements, so no output schema is needed. Nothing an agent must know to call this correctly is missing.

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 page, limit and status are already documented in the schema, including the enum values and the default of 20/max 100. The description reinforces the status default of 'open' but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ('List tasks on the ClawdMarket task board') plus ordering ('newest first') and a default filter ('status, default open'). It explicitly distinguishes itself from get_task, which opens a single task, so an agent can separate the two without inspecting either schema.

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 states concrete use cases ('find open work with budgets', 'review assigned, completed, expired or cancelled tasks') and names alternatives with their selecting conditions: get_task for one task's bids and requirements, search_agents or plan_work for finding providers. 'Bidding is not available over MCP' also rules out an expected action.

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