Skip to main content
Glama

List work requests

list_work_requests
Read-onlyIdempotent

List work requests (submitted by requesters). Filter by status (PENDING_REVIEW, APPROVED, REJECTED) or priority.

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
pageNoPage number (default: all pages fetched automatically)
searchNoSearch by name
statusNoFilter by status: PENDING_REVIEW, APPROVED, REJECTED
site_idNoFilter by site ID - resolve via list_sites
per_pageNoItems per page (default: 1000, max: 1000). All pages are fetched automatically.
priorityNoFilter by priority: LOW, MEDIUM, HIGH, URGENT

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site_id / description
      Previous value: -"Filter by site ID"New value: +"Filter by site ID - resolve via list_sites"
  2. Changed2 schema fields changed
    • changedInput schema / properties / priority / description
      Previous value: -"Filter by priority: LOW, MEDIUM, HIGH, CRITICAL"New value: +"Filter by priority: LOW, MEDIUM, HIGH, URGENT"
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status: SUBMITTED, APPROVED, REJECTED, CONVERTED"New value: +"Filter by status: PENDING_REVIEW, APPROVED, REJECTED"
  3. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / site_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  4. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / page / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / site_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  5. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / site_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$"
  6. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is carried for free. The description adds nothing beyond that – notably it omits the notable fact (documented only in the schema) that all pages are fetched automatically, and says nothing about result ordering, defaults, or volume.

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 sentence front-loading the verb and resource with the filters appended. Nothing wasteful, though it is arguably under-written rather than well-sized for a 6-parameter listing tool.

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?

No output schema and no pagination/return-shape explanation in the description; the auto-fetch-all-pages behavior is a meaningful listing trait that lives only in a parameter description. Adequate but leaves gaps an agent would want filled.

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 100%, so page, per_page, search, site_id and status/priority values are already documented, including the list_sites resolution hint. The description repeats enum values for status/priority but adds no syntax, default, or interaction detail beyond the schema. Baseline 3 applies.

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?

Specific verb+resource ('List work requests') plus a scoping note that they are submitted by requesters, which distinguishes this from list_work_orders. It doesn't explicitly name the sibling work-order tool, but the resource itself is unambiguous.

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?

Implies usage through the filter list (status, priority) but never states when to choose this over get_work_request, list_work_orders, or list_sites for site resolution. No exclusions or prerequisites are given.

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