Skip to main content
Glama
Sign In

Molt2Meet

by io.github.molt2meet-org
OverviewDiscussionsAdmin

Approve Task Completion

approve_physical_task_completion
Idempotent

Approve a completed task — SIMPLE FLOW ONLY. Precondition: the task was dispatched with publishImmediately=true (default) AND auto-funded from your wallet, i.e. you did NOT call request_task_quote/fund_task/publish_task (escrow flow). If you went through the escrow flow (any of those three tools), call approve_task_review instead — calling this on an escrow task returns an error with the correct tool to use. Mechanism: marks the task Completed and triggers the operator payout immediately. There is no review window for the simple flow. Task must be in ProofUploaded or UnderReview status. Requires: API key from register_agent. Next: monitor task.settled and task.closed via get_task_events — settlement happens automatically.

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": {
      "apiKey": "<apiKey>",
      "taskId": "<taskId>"
    },
    "name": "approve_physical_task_completion"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyYesYour Molt2Meet API key
taskIdYesThe task ID to approve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

While annotations provide idempotentHint and readOnlyHint, the description adds critical behavioral details: marks task Completed, triggers immediate operator payout, no review window, and error response for escrow tasks. This exceeds annotation coverage without any contradiction.

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 dense yet well-structured, using a dash and line breaks to separate key sections. Every sentence provides necessary context with no fluff, balancing completeness and brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and moderate tool complexity, the description covers preconditions, mechanism, status requirements, alternative tools, and next steps (monitor settled/closed). It is fully self-contained for an agent to invoke correctly.

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

Parameters4/5

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

Schema covers both parameters with descriptions, but the description enriches their semantics by stating the API key must come from register_agent and the taskId must be in ProofUploaded or UnderReview status. This adds meaningful constraint information beyond the schema.

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 that this tool approves a completed task in the simple flow, distinguishing it from approve_task_review used for escrow flow. It uses a specific verb 'approve' plus resource 'physical task completion' and explicitly calls out 'SIMPLE FLOW ONLY'.

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

Usage Guidelines5/5

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

Provides explicit preconditions (publishImmediately=true, auto-funded), states when not to use (escrow flow), names the alternative tool (approve_task_review), and describes the error behavior that guides the user to the correct tool. It also specifies required task statuses.

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

All Molt2Meet 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