Skip to main content
Glama

Somon.tj 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 ru, tg. Default ru.
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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuine value by disclosing the returned field groups and the deliberate omission of seller contact data. It says nothing about failure behavior for a bad or stale advert_id, which is the main remaining behavioral gap.

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 short clauses with zero filler, front-loaded with the payoff (what you get) and followed by the one constraint that would otherwise waste a call. Every sentence earns its place.

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 an output schema present and annotations covering the safety profile, the description need only frame scope and boundaries — which it does. The only missing element an agent might want is what happens on an invalid or removed listing.

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%, so both parameters are already documented, including the ru/tg language values and the fact that advert_id may be a listing URL. The description adds no parameter-level meaning beyond the schema, which is the baseline 3 case.

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 names the resource (a listing) and enumerates the payload contents (description, attributes, photos, seller), which tells an agent precisely what it gets back. It is slightly weaker on the verb/scope side — 'Listing details' borders on restating the title — but combined with the required advert_id the intent is unambiguous.

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 explicitly carves out the contact case and routes it to the sibling: 'No contacts: use reveal_contact.' That is a real when-not/alternative pairing. It does not state the common entry path (call after search_adverts to expand a result), so it stops short of full routing guidance.

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