Skip to main content
Glama

Piko

Prepare a Piko listing

prepare_listing

Stores a draft of a listing for 24 hours and returns a pikosabe.com link to it. Nothing is published by this tool: the person opens the link, signs in to Piko with their phone, reviews the prefilled form and publishes it themselves. The draft is checked against the rules of the publishing form (title and description lengths, currency of the market, no phone number in the text). The listing is located at the place confirmed in the person's Piko profile, so the draft carries no city.

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": {
      "country": "<country>",
      "side": "<side>",
      "type": "<type>",
      "title": "<title>"
    },
    "name": "prepare_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNoPresent when the listing is a position an employer wants to fill (a nanny, a shop assistant). It goes with side demand and type service.
sideYesoffer: the person offers a service or has something to sell or rent out. demand: the person is looking for a service, a thing or someone to hire.
typeYesListing type. rental is a thing rented out by the day or week; housing for sale or rent is property.
titleYesListing title in Spanish, 10 to 60 characters, for example "Electricista matriculado a domicilio".
countryYesMarket to read: PY = Paraguay, BO = Bolivia. Results stay within that market.
descriptionNoDetails in Spanish, up to 1000 characters, in the person's own terms. Optional.
transactionNoGoods offered: sale, free or exchange. Property offered or wanted: sale or rental. Pets offered or wanted: sale or free (adoption). Other types have no transaction.
price_amountNoPrice for an offer, pay for a position, maximum budget for another demand. Omitted when the person gave no amount.
price_currencyNoCurrency code of the amount. By market: PY PYG or USD, BO BOB or USD. Omitted: the market's own currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description adds substantial behavioral context beyond the annotations: the draft is stored for 24 hours, a pikosabe.com link is returned, nothing is published, the draft is validated against publishing rules, and the location comes from the person's profile so no city is included. It does not cover failure behavior when validation fails or authentication requirements, keeping it short of a 5.

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 four tightly packed sentences with zero waste. It front-loads the core action and return value, then immediately clarifies the no-publishing behavior, validation checks, and location derivation in a logical order.

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?

Given nine parameters, a nested object, and no output schema, the description covers the key return value (a draft link), TTL, safety behavior, validation, and the location rule. It is complete enough for an agent to call correctly, though it could mention error handling or authentication to be fully comprehensive.

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?

With 100% schema description coverage, the schema already documents all parameters including enums and nested job fields. The description adds a useful note that the listing location comes from the Piko profile and therefore carries no city parameter, but it does not otherwise deepen understanding of the remaining parameters beyond what the schema provides.

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 and resource: it stores a draft listing and returns a link. It explicitly distinguishes this tool from publishing, making clear it is a preparatory step rather than a live listing action, which separates it from siblings like show_listing and search.

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?

It clearly indicates the tool is for preparing a draft that a person later reviews and publishes themselves, and it rules out publishing. However, it does not explicitly name alternative tools or state when to use a different sibling instead, leaving some routing inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources