Skip to main content
Glama

get_work_agreement_template

Read an opt-in linked grant template for the selected direct-prepayment proposal. No execution or payment is created. Protected inspections use their separate protected handoff.

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_agreement_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does usefully disclose that 'no execution or payment is created' and that protected inspections are routed elsewhere, but it says nothing about authorization requirements, whether the template is null when no proposal is selected, or what the returned structure 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 action and its side-effect disclaimer, with no filler. It loses a point only because the compressed jargon makes the sentences less parseable than their length suggests.

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 tool with no annotations, no output schema, and an undocumented identifier parameter, the description should explain at minimum what the template contains and what requestId scopes. The safety note about no execution/payment is the only substantive disclosure, leaving the return contract entirely unstated.

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?

There is one required parameter, requestId, and schema description coverage is 0%, so the description must compensate and does not. It never explains whether requestId refers to the proposal, the work request, or the template lookup itself — a meaningful ambiguity given the tool's dependency on a 'selected' proposal.

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 verb ('Read') and resource ('grant template') are stated, and the scope is narrowed to a 'selected direct-prepayment proposal'. However, the resource is described in dense domain jargon ('opt-in linked grant template', 'protected handoff') that an agent cannot resolve without prior knowledge, and nothing distinguishes this read from siblings like get_prepared_offer_terms or read_work_execution.

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 stated condition for when to call this versus the many other read tools in the sibling list. The clause 'Protected inspections use their separate protected handoff' implies an alternative exists but never names it or states the routing condition, leaving the agent to guess.

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