Skip to main content
Glama

work_decision_terms

Buyer: get exact escrow-domain EIP-712 WorkDecision for the current delivery and round. Choose approved yourself after downloading. Rejecting the third delivery applies the funded finalProviderBps.

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>",
      "approved": "<approved>"
    },
    "name": "work_decision_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
approvedYes
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses that rejecting the third delivery applies the funded `finalProviderBps`, but it does not clarify read-only vs mutating status, authorization requirements, error behavior, or what the returned WorkDecision contains.

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?

The description is front-loaded and only three sentences long, with little wasted text. The phrase 'after downloading' is ambiguous and the domain jargon makes it denser than ideal, but the structure 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?

This is a complex escrow/EIP-712 tool with no annotations, no output schema, and 0% parameter description coverage. The description adds an important domain rule but leaves key gaps around `requestId`, the shape of the WorkDecision, and the tool's operational behavior.

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 0%, so the description needs to explain both parameters. It only obliquely references `approved` through the third-delivery rejection rule, and `requestId` is entirely undocumented in both schema and description.

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?

The description uses a specific verb and resource: get the exact escrow-domain EIP-712 WorkDecision for the current delivery and round. It is clear what the tool retrieves, but it does not explicitly distinguish itself from related siblings such as typed_data or decide_work.

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?

It identifies the buyer role and scopes usage to the current delivery and round, and says to choose `approved` yourself after downloading. However, it does not explicitly state when not to use it or which sibling to use for related actions such as deciding or retrieving typed data.

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