Skip to main content
Glama

create_work_request_selection_challenge

Inspect and sign exact fresh-work proposal terms. Selection returns a direct Work Ticket template or protected inspection handoff according to the proposal; each requires separate signatures and payment.

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>",
      "buyer": "<buyer>",
      "proposalId": "<proposalId>"
    },
    "name": "create_work_request_selection_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYes
requestIdYes
proposalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations, the description bears the full burden. It does disclose two useful traits — that selection yields either a Work Ticket template or an inspection handoff, and that each path requires separate signatures and payment — but it omits what a 'challenge' is, whether it is idempotent, what permissions the buyer needs, or what the caller must do with the returned terms.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, reasonably front-loaded, but dense domain jargon ('fresh-work proposal terms', 'protected inspection handoff') that trades clarity for brevity. No wasted filler, yet the compression costs comprehension.

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?

No annotations, no output schema, and zero parameter coverage mean the description must carry everything, and it does not. For a three-required-parameter mutation-style tool, key facts about inputs, return shape, and side effects are missing.

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

Parameters1/5

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

Schema description coverage is 0% and all three required parameters (requestId, buyer, proposalId) are undocumented in both schema and description. The description never references any parameter, so the agent gets no meaning for the UUID identifiers or the buyer address beyond their names.

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?

The description names a concrete act ('Inspect and sign exact fresh-work proposal terms') and an outcome branch (direct Work Ticket template vs. protected inspection handoff), but never states the tool's actual operation — creating a selection challenge — nor distinguishes it from near-identical siblings like create_work_request_challenge or select_work_request_proposal. An agent can infer domain but not the precise verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites (beyond a passing note that signatures and payment are required), and no routing to alternatives such as select_work_request_proposal or the sibling challenge endpoints. The agent must guess which of the many challenge-creation tools applies.

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