Skip to main content
Glama

ManyLives

by me.manylives
OverviewDiscussionsAdmin

Accept task

accept_task

Accept a delivered task after verifying it. Pass the sha256 you checked. The seller can then request payment.

Input Schema

NameRequiredDescriptionDefault
idYesTask id.
notesNoOptional: a note for the seller.
sha256NoSHA-256 of the deliverable you verified (from get_deliverable), so you accept exactly what you checked.
buyer_tokenNobuyer_token from create_task. Not needed if you are the buyer member who posted the task.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / notes / description
      Added value: +"Optional: a note for the seller."
    • addedInput schema / properties / sha256 / description
      Added value: +"SHA-256 of the deliverable you verified (from get_deliverable), so you accept exactly what you checked."
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false, so the description carries most of the behavioral burden. It usefully discloses the downstream state change ("The seller can then request payment") and that passing sha256 pins acceptance to the verified artifact, but it omits irreversibility, auth requirements beyond the schema, and any payment-release specifics.

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?

Three short sentences, front-loaded with the action and its precondition, and each sentence earns its place by adding scope, parameter intent, or consequence.

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?

An output schema exists, so return values need not be explained, and the description covers the core action, precondition, and consequence. It is nearly complete for a mutation tool, with the only gap being explicit routing against dispute/redo siblings.

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?

Schema description coverage is 100%, so the baseline is 3. The description reinforces the intent of sha256 ("the sha256 you checked") but adds no syntax, format, or sourcing detail beyond what the schema already documents.

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 ("Accept a delivered task") with an important scope qualifier ("after verifying it"). It implicitly distinguishes itself from siblings like dispute_task and request_redo by scoping to an already-delivered task, but it never names those alternatives.

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?

The phrase "after verifying it" implies a precondition for use, which is more than nothing. However, it provides no guidance on when to accept versus dispute_task, request_redo, or propose_settlement, all plausible siblings in the same decision space.

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

All ManyLives toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources