Skip to main content
Glama

Piko

Show a Piko listing

show_listing
Read-onlyIdempotent

Returns one active listing by its id: title, description, price, place, owner and its pikosabe.com link. 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": {
      "listing_id": "<listing_id>",
      "country": "<country>"
    },
    "name": "show_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesMarket to read: PY = Paraguay, BO = Bolivia. Results stay within that market.
listing_idYesListing id, as returned by search or show_profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description's contribution is the data-scope disclosure: no phone number is returned and contact happens on the pikosabe.com page. That is genuinely useful behavioral context an agent cannot derive from the schema. It stops short of describing the not-found behavior, which keeps it off 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?

Two sentences with zero filler: the first front-loads the operation and its return shape, the second immediately qualifies a limitation the agent would otherwise assume away. Nothing is repeated and nothing needs trimming.

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 correctly substitutes by enumerating returned fields and flagging the missing phone number. It is nearly complete for a two-parameter read tool, but leaves the error/not-found path and the meaning of 'active' implicit.

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%, with the country enum and the listing_id uuid pattern and provenance ("as returned by search or show_profile") fully documented in the schema. The description adds only the phrase "by its id" and never mentions the country parameter at all, so it does nothing beyond the structured fields.

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 and resource with cardinality and lookup key: "Returns one active listing by its id," then enumerates the returned fields (title, description, price, place, owner, link). The singular, id-based framing contrasts naturally with the sibling 'search', so an agent can tell the two apart without opening either schema.

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 id-only lookup and the 'active listing' qualifier suggest when this beats a search, and the closing sentence tells the agent what to do after (contact via the pikosabe.com page). There is no explicit statement of when to prefer show_profile or prepare_listing, or of what happens for an inactive or unknown id.

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