Skip to main content
Glama

Piko

Search Piko

search
Read-onlyIdempotent

Searches the Piko marketplace in one country, by meaning and by exact words. Returns at most 5 providers or 10 listings from real accounts, ordered by relevance, each with its pikosabe.com link. Listings that are job openings or job seekers' offers carry a job field with the working arrangement and the pay when stated. A count of 0 means no listing matches these terms. Results carry no phone number: contact happens on the pikosabe.com page of the listing or profile.

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": {
      "mode": "<mode>",
      "query": "<query>",
      "country": "<country>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoLimits the search to this city, for example "Asunción".
modeYesproviders: people who offer a service, grouped by profile. listings: individual published offers or demands of any type.
sideNoListings mode only. offer: things and services people offer. demand: things and services people are looking for. Omitted: both.
queryYesWhat is searched: a short phrase such as "plomero", "auto usado" or "Toyota Hilux". Listings are written in Spanish, so a Spanish phrase matches best.
typesNoListings mode only. Limits the search to these listing types.
countryYesMarket to read: PY = Paraguay, BO = Bolivia. Results stay within that market.
job_seekersNotrue: only job seekers, the providers who marked a service offer as available for a job, with the arrangement and the pay they expect when stated. They are offer listings of type service; mode, side and types are set accordingly. Not combined with job_openings.
job_openingsNotrue: only job openings, the positions an employer wants to fill (a nanny, a shop assistant). They are demand listings of type service; mode, side and types are set accordingly.
neighborhoodNoLimits the search to this neighborhood of the city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: result caps (at most 5 providers, 10 listings), relevance ordering, guaranteed link on each result, presence of a job field with arrangement and pay, and the notable constraint that no phone numbers are returned and contact happens on pikosabe.com. That last point is exactly the kind of non-obvious operational fact annotations cannot convey. Missing only latency/rate or freshness caveats.

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?

Four sentences, front-loaded with what is searched and what comes back, then the job-field note, then the zero-count and no-phone caveats. Every sentence earns its place; the job-field sentence is slightly dense but not padded.

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?

With 9 parameters, 3 required, and no output schema, the description correctly takes on the burden of describing return shape: caps, ordering, per-result link, the job field's contents, and the meaning of a zero count. Enough for an agent to call it confidently; the omission of how providers versus listings results differ structurally is the main residual gap.

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 description coverage is 100% and the enum/field semantics for mode, side, types, country, job_seekers and job_openings are already fully documented in the schema. The description adds little parameter-level meaning beyond "in one country" (signalling country is required) and the Spanish-language matching hint that the schema also carries. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Searches the Piko marketplace in one country") plus the matching mode (by meaning and exact words), which distinguishes it from nothing else explicitly but makes the operation unmistakable. Sibling names (show_listing, show_profile, prepare_listing) suggest a read-vs-detail split the description does not articulate, keeping it just short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the description makes clear you search to find providers or listings, and notes that a count of 0 means no match, but it never says when to reach for this versus show_listing or show_profile, nor does it state prerequisites. The mode/side/type routing guidance lives entirely in the schema descriptions rather than here.

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