Skip to main content
Glama
Sign In

Freelance Clearing

by com.freelanceclearing
OverviewDiscussionsAdmin

Request work from an offer

send_request
Destructive

Ask a seller to do something, naming your own amount and how long you expect it to take. Requires a verified email and a saved payment method: a request is a commitment to pay if the seller accepts. NOTHING IS CHARGED NOW -- if this credential has a spending limit, the amount is reserved against it and released if the seller declines. One pending request per buyer per SELLER, so you cannot queue two with the same person; you cannot request your own offer; and the offer must still be active. The request is private between the two of you at every stage.

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": {
      "offer_id": "<offer_id>",
      "amount": "<amount>",
      "estimated_days": "<estimated_days>",
      "description": "<description>"
    },
    "name": "send_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesWhat you will pay, in dollars. Positive. The starting price is a guide, not a floor.
offer_idYesThe offer's UUID
descriptionYesWhat you need. Only the seller sees it.
estimated_daysYesHow long you expect it to take. A positive whole number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and non-idempotent, but the description carries the real behavioral weight: nothing is charged now, the amount is reserved against a spending limit and released on decline, and the request is a binding commitment to pay if accepted. It also discloses the privacy scope ('private between the two of you at every stage'), which no annotation covers.

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?

Front-loads the core action, then the prerequisites, then the payment mechanics, then the constraints. Dense but each sentence carries distinct information; the capitalized NOTHING IS CHARGED NOW is a justified emphasis rather than filler.

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?

For a non-idempotent, destructive mutation with no output schema, the description covers financial consequences, eligibility, concurrency limits, and privacy. The main gap is that it does not say what the call returns or how to later reference the created request, which matters given there is no output schema.

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 coverage is 100%, so all four parameters are already documented in the schema, including the useful note that the starting price is a guide not a floor. The description only paraphrases amount and estimated_days at a high level, adding no format or constraint detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Ask a seller to do something') and immediately scopes it with the two inputs the buyer controls: amount and expected duration. This distinguishes it from the bid-side siblings like submit_bid, which flow in the opposite direction.

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

Usage Guidelines4/5

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

Gives strong eligibility context: verified email plus saved payment method required, one pending request per buyer per seller, no self-requests, and the offer must still be active. It never names an alternative sibling (e.g. submit_bid or accept_request) to route against, so it stops short of full when/when-not/alternatives guidance.

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

All Freelance Clearing 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