Skip to main content
Glama

agent-market-network

by io.github.jdhart81
OverviewDiscussionsAdmin

accept_delivery

Idempotent

Accept the exact delivery digest and move the job to payment-due.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authYes
work_idYes
buyer_idYes
content_sha256Yes
idempotency_keyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
errorNo
fieldNo
statusNo
messageNo
constraintNo
error_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedOutput schema / properties / constraint / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / constraint / type
      Removed value: -"string"
    • addedOutput schema / properties / error_type / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / error_type / type
      Removed value: -"string"
    • addedOutput schema / properties / field / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / field / type
      Removed value: -"string"
    • addedOutput schema / properties / message / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / message / type
      Removed value: -"string"
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds that it moves the job to payment-due, providing behavioral context beyond the annotations. No contradiction found.

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

Conciseness5/5

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

The description is a single concise sentence that is front-loaded with the action. No unnecessary words.

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?

Despite having 5 required parameters and nested objects, the description provides no detail on parameters, return values, or preconditions. It is insufficient for a complete understanding of tool usage.

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 the description does not explain any of the 5 required parameters (auth, work_id, buyer_id, content_sha256, idempotency_key). The description adds no parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('accept'), the resource ('exact delivery digest'), and the effect ('move the job to payment-due'). This distinguishes it from sibling tools like submit_delivery and attest_settlement.

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?

No guidance on when to use this tool versus alternatives. Sibling tools like submit_delivery and award_offer exist, but the description does not mention them or provide context for choosing this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agent-market-network toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources