Skip to main content
Glama

Piko

Show a Piko profile

show_profile
Read-onlyIdempotent

Returns one public profile, found by user id or by name or @nickname: biography, place, rating, recent reviews, active offers and demands, and its pikosabe.com link. When several profiles match a name, returns the list of matches instead. 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": {
      "country": "<country>"
    },
    "name": "show_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoName or @nickname, for example "Teresa" or "@juanito". Used when no user_id is known.
countryYesMarket to read: PY = Paraguay, BO = Bolivia. Results stay within that market.
user_idNoUser id, as returned by search.

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?

The annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description's added value is what it says beyond them: that multiple matches return a collection instead of a single object, and that no phone numbers are exposed because contact is routed to the pikosabe.com page. Both are non-obvious behavioral facts worth knowing before calling.

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?

Three sentences ordered by importance: what is returned, the multi-match edge case, then the privacy/contact rule. No filler, though the contact-policy sentence is the least essential and could be trimmed.

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 no output schema, the description carries the burden of describing the response and does so by enumerating the returned fields and flagging the alternate list-of-matches shape. Pagination and field-level detail are absent but not critical for this lookup.

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 each parameter already carries a description including enum meanings and UUID format, so the baseline is 3. The description only reinforces the query/user_id relationship already documented in the schema, adding no new syntax or constraint.

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?

The description opens with a concrete verb and resource ("Returns one public profile") and enumerates the lookup keys and payload fields, so an agent can tell this apart from search or listing tools. It stops short of naming a sibling it replaces or defers to, leaving the differentiation implicit.

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?

It states the input path to use (user id vs. name/@nickname, "Used when no user_id is known") and warns that an ambiguous name yields a list of matches rather than one profile. There is no explicit when-not-to-use guidance or pointer to search/show_listing for building a profile, so selection logic must be inferred.

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