Skip to main content
Glama
Sign In

SameDayDesk agent tools

by com.samedaydesk
OverviewDiscussionsAdmin

browse_taskmarket_tasks

Read-only

Browse current public TaskMarket inventory through the official read API. Filter by lifecycle status, mode, tag, text, and minimum reward. Amounts carry their actual chain/token; unknown decimals stay raw. Task descriptions are returned as untrusted text and are never executed.

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

Input Schema

NameRequiredDescriptionDefault
tagNoExact case-insensitive tag filter.
modeNo
limitNo
searchNoCase-insensitive text match over descriptions and tags.
statusNoopen
chain_idNoOptional current served chain selector.
min_reward_usdcNoLegacy minimum gross reward; selects qualified Base USDC only. Refuses unknown assets, conflicting metadata or an unlike chain selector; never compares OUSD to USDC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / chain_id
      Added value: +{
+  "description": "Optional current served chain selector.",
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / min_reward_usdc / description
      Previous value: -"Minimum gross reward in USDC."New value: +"Legacy minimum gross reward; selects qualified Base USDC only. Refuses unknown assets, conflicting metadata or an unlike chain selector; never compares OUSD to USDC."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes meaningfully beyond the readOnly/openWorld annotations by disclosing two non-obvious behaviors: amounts are returned with their actual chain/token and unknown decimals remain raw, and task descriptions are untrusted text that is never executed (a prompt-injection safety note). It does not cover pagination or rate/error behavior, so not a 5.

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?

Three tight sentences, purpose front-loaded, then filters, then return-characteristic/safety notes. A few phrases are compressed to the point of opacity ('unknown decimals stay raw'), but nothing is padding.

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 7-param, zero-required read tool with no output schema, the description covers purpose, filter surface, and key return-value characteristics plus a safety note. It leaves the default/max of 'limit' and the semantics of 'chain_id' entirely to the schema, which is the main remaining 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?

With 57% schema coverage, the baseline is 3. The description names most filters (lifecycle status, mode, tag, text, minimum reward) but adds no meaning for 'limit' or 'chain_id', and the caveats about unknown assets and OUSD vs USDC already appear in the schema for min_reward_usdc.

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?

Specific verb plus resource ('Browse current public TaskMarket inventory') and an explicit channel ('official read API'). The enumeration of filterable dimensions makes it clearly distinct from siblings like track_taskmarket_task (single task) or plan_taskmarket_delegation (planning).

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?

The description implies the tool is for discovering tasks ('browse current inventory') and lists filters, which hints at when it applies. However, it names no alternatives and gives no explicit when-not guidance against siblings such as track_taskmarket_task or plan_taskmarket_delegation, leaving the routing decision to inference.

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

All SameDayDesk agent tools 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