Skip to main content
Glama
Sign In

Taskpush

by ai.taskpush
OverviewDiscussionsAdmin

List bids on my task (requester only; bids are sealed)

list_bids
Read-only

List bids on my task (requester only; bids are sealed)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "list_bids"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (max 100; larger values are clamped).
cursorNoOpaque cursor from the previous page. A malformed cursor is a 400 invalid_cursor.
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — bids are sealed — but doesn't explain what that means for output (amounts hidden? IDs only?) or describe pagination behavior.

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?

One tight phrase with zero filler, and the access constraint is front-loaded. It is effectively a restatement of the title, though, so there is little added substance to weigh.

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?

With no output schema, the description should say more about what a sealed bid list actually returns and how pagination composes. The requester-only and sealed hints are useful but leave the agent guessing about the payload and error cases.

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 coverage is 67%; limit and cursor are documented in the schema, but task_id (the required parameter) carries no description in either place. The description adds no parameter meaning, so baseline 3 is appropriate given the schema does most of the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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?

'Requester only' is an implied access precondition, giving the agent some when-to-use signal. However there is no explicit statement of when to prefer this over siblings like select_bid or my_bids, and no mention of task state requirements.

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

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