Skip to main content
Glama

Unegui.mn classifieds

Listing details

get_advert
Read-only

Listing details: description, attributes, photos, seller. No contacts: use reveal_contact.

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": {
      "advert_id": "<advert_id>"
    },
    "name": "get_advert"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of listing texts: one of mn. Default mn.
advert_idYesadvert_id from search_adverts, or a listing url.

Output Schema

NameRequiredDescriptionDefault
urlYes
priceNo
titleYes
photosNo
sellerYes
locationNo
advert_idYesPass to reveal_contact as is.
publishedNo
attributesNo
price_noteNo
descriptionNo
category_pathNo
contact_channelsNoChannels the seller accepts; call reveal_contact to get them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and an output schema exists, so the baseline burden is low. The description still adds real value by delimiting the returned scope and stating that contact data is deliberately excluded, but it says nothing about auth needs, rate limits, or partial/missing records.

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 telegraphic fragments with zero waste, front-loading what the agent gets and then the one exclusion that prevents a wrong call. Nothing could be removed without losing routing information.

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 single-record read with a full schema, complete annotations, and an output schema, the description covers the essentials: what comes back and where to go for contacts. The only gap is that the trigger relationship with search_adverts is left to the schema.

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%, with advert_id documented as coming from search_adverts or a listing URL, and language documented with its default. The description adds no additional parameter meaning, so the baseline 3 applies.

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?

"Listing details: description, attributes, photos, seller" names the resource and the exact payload it returns, so an agent knows this fetches a single listing's full record. It also separates itself from reveal_contact, though the action verb itself is only implied by the tool name.

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 gives an explicit when-not and a named alternative: "No contacts: use reveal_contact." The positive trigger (call this after search_adverts to expand one result into full details) is only implied, carried partly by the advert_id schema note rather than the description.

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