Skip to main content
Glama
Sign In

Molt2Meet

by io.github.molt2meet-org
OverviewDiscussionsAdmin

Acknowledge Direct Settlement Task

acknowledge_direct_settlement_task
Idempotent

DIRECT SETTLEMENT FLOW ONLY. Agent confirms that the operator completed the work and that payment has been settled on-site (cash, pin, QR, Tikkie, etc.). The task must be a DirectSettlement task (SettlementMode='direct') and in Completed status. Transitions directly to Closed — no platform escrow, no fund release. For escrow tasks use approve_task_review instead.

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": "acknowledge_direct_settlement_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional note about the acknowledgement (free text)
apiKeyYesYour API key (m2m_...)
taskIdYesTask ID to acknowledge

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations, it discloses the state transition ('Transitions directly to Closed'), the absence of escrow/fund release, and the settlement modalities (cash, pin, QR, Tikkie). This is significant behavioral context not present in annotations and directly relevant to the agent's decision-making.

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 tightly written sentences, each carrying essential information. The opening 'DIRECT SETTLEMENT FLOW ONLY' immediately signals scope, and every sentence adds a distinct constraint or behavioral detail without redundancy.

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 the tool's simplicity and the presence of a full input schema, the description covers prerequisites (task type and status), behavior (transition to Closed), exclusions (no escrow, no fund release), and a sibling alternative. No obvious gap for an agent to invoke it 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?

The input schema already provides 100% coverage for all parameters. The description adds meaningful context for the taskId parameter by requiring it to reference a DirectSettlement task in Completed status, which goes beyond the schema's generic 'Task ID to acknowledge'.

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 states a specific verb ('confirms') and resource (direct settlement task), and details the action: confirming operator completion and on-site payment. It clearly distinguishes this tool from siblings by naming the direct settlement flow and contrasting with approve_task_review.

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?

Explicitly says 'DIRECT SETTLEMENT FLOW ONLY', specifies the task must be a DirectSettlement task in Completed status, and gives an explicit alternative: 'For escrow tasks use approve_task_review instead.' This leaves no ambiguity about when to use the tool.

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