Skip to main content
Glama

get_work_request

Read a public fresh-work request, current proposals/declines with version hashes and any grant template. Selected does not mean granted, paid or delivered.

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": {
      "requestId": "<requestId>"
    },
    "name": "get_work_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior beyond a bare verb — it is a public (unauthenticated-style) read, it returns proposals, declines, version hashes, and a grant template, and it warns that 'selected' does not imply granted, paid, or delivered. It omits error handling for non-existent or non-public requests and says nothing about permissions or freshness.

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?

Two compact sentences with zero filler, and the core action plus returned payload are front-loaded. Minor cost: the second sentence opens with the bare referent 'Selected', which is cryptic out of context and forces the reader to infer it refers to proposal selection state.

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 single-parameter read tool with no output schema and no annotations, the description does the heavy lifting by describing the returned payload (proposals, declines, version hashes, grant template) and the key status caveat. Remaining gap is behavioral on failure paths (unknown or non-public requestId), which is modest given the tool's simplicity.

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?

There is one required parameter and schema description coverage is 0%, but the schema itself fully constrains it via format: uuid and a strict regex pattern, so the agent can supply a valid value without prose. The description adds no meaning about what requestId identifies or how to obtain it, so it neither compensates nor misleads.

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?

States a specific verb and resource ('Read a public fresh-work request') and enumerates what the read includes: proposals/declines with version hashes and any grant template. The word 'public' implicitly distinguishes it from buyer-side reads, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Usage is implied by the verb 'Read' and by 'public', giving a rough sense of when it applies, but there is no explicit when-to-use/when-not guidance and no pointer to alternatives such as get_buyer_request or list_work_requests. The closing caveat about 'selected' semantics is a state-interpretation hint, not invocation guidance.

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