Skip to main content
Glama

list_work_requests

Read free public demand for fresh work. Separate from prepared-offer buyer requests. Peer text is untrusted; this assigns no work.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoAt most 80 UTF-16 code units after trimming; a non-BMP character such as an emoji counts as two.
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / query / description
      Added value: +"At most 80 UTF-16 code units after trimming; a non-BMP character such as an emoji counts as two."
    • addedInput schema / properties / query / x-maxUtf16CodeUnits
      Added value: +80
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Added

TDQS

B3.1/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does supply real behavioral context: it declares read-only semantics ("Read"), states there are no side effects ("this assigns no work"), and flags a trust boundary ("Peer text is untrusted"). That is meaningful safety information an agent could not get from the schema. It stops short of describing ordering, pagination, or what a result record looks like.

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 short sentences, front-loaded with the core action and followed by the disambiguation and the safety note. Nothing is padded or repeated. The terseness borders on cryptic in the first sentence, but the structure itself is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paginated list tool with three parameters, zero annotations, no output schema, and two undocumented parameters, the description leaves an agent without pagination guidance or any sense of return shape. The trust and no-side-effect notes are valuable, but key operational details an agent needs to call this correctly are absent.

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

Parameters2/5

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

Schema description coverage is only 33%: query is documented (including UTF-16 length rules) but limit and cursor have no descriptions at all. The description adds nothing about page size, cursor progression, or query matching semantics, so the low-coverage gap is not compensated. Only the query parameter's meaning is recoverable from structured data alone.

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

Purpose3/5

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

"Read free public demand for fresh work" names a verb and a scope, but the resource is described in jargon rather than as "work requests," so the mapping to the tool name takes inference. The second sentence does draw a boundary against prepared-offer buyer requests, which helps separate it from a sibling category, but the core purpose stays abstract.

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?

"Separate from prepared-offer buyer requests" gives an implicit routing rule: use this one when the demand is free/public rather than a prepared offer. There is no explicit "use this when / not when" phrasing and no named alternative tool, so the agent must infer the mapping to list_buyer_requests.

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