Skip to main content
Glama
Sign In

Mercadopleis

by io.github.castiquark
OverviewDiscussionsAdmin

post_request

Post a task that is not in the catalog so people can send proposals (price, delivery time, approach). Use it when search_services finds nothing that fits; its result includes a draft. Requires login. The request is public: do not include secrets or private data; send those later with send_message to the chosen seller.

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": {
      "title": "<title>",
      "description": "<description>",
      "category": "<category>",
      "budgetUsdc": "<budgetUsdc>",
      "deliveryDays": "<deliveryDays>"
    },
    "name": "post_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
categoryYesai_data | development | writing_translation | consulting | design | marketing | security_audit | video_audio | legal_finance | others
budgetUsdcYesMaximum you are willing to pay
descriptionYesInput you provide, expected output and format, quality criteria
deliveryDaysYes
sessionTokenNoThe sessionToken returned by login. Treat it as a secret: never share it or put it in messages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses login requirement, that the result includes a draft, and that the request is publicly visible (with a secrets warning). It omits fee/cost implications, editability, and moderation/lifecycle behavior a publisher would want to know.

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 dense sentences, front-loaded with purpose, then usage condition, then constraints. Every clause earns its place with no 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 6-param mutation tool with no annotations and no output schema, the description covers purpose, trigger, auth, public-visibility risk, and a return hint ('includes a draft'). It could say more about the created request's identifier or subsequent workflow, but the essentials for correct invocation are present.

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 67%, so the schema documents category, budgetUsdc, deliveryDays, and sessionToken. The description's mention of 'price, delivery time, approach' loosely maps to budget/delivery parameters but adds no format, bounds, or enum detail beyond the schema; baseline 3 fits.

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?

Specific verb+resource ('Post a task that is not in the catalog') with the downstream effect stated (people send proposals). It clearly distinguishes itself from siblings like search_services, create_order, and send_proposal.

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?

Gives an explicit trigger: 'Use it when search_services finds nothing that fits,' naming the alternative and the condition that selects this tool. It also routes follow-up behavior to send_message for sensitive data.

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

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