Skip to main content
Glama

Detail inzerátu / Get listing

get_listing
Read-onlyIdempotent

Vráti jeden zverejnený inzerát podľa id (schéma listing v1) a jeho verejnú adresu. Returns one published listing by id (listing v1 schema) with its public_url. No API key needed.

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": {
      "id": "<id>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesID inzerátu, napr. 'bm-pozemok-mokrance'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful facts beyond that: only published listings are returned, and no API key is required. It says nothing about the shape of the error or the response beyond the schema name.

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?

Two short sentences with the behavior front-loaded and no filler. The Slovak and English lines are near-duplicates, which is mild redundancy but arguably justified for a bilingual catalog.

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-parameter read tool the description covers purpose, payload ('listing v1 schema' plus public_url) and authentication, which compensates for the absent output schema. Only the unpublished/unknown-id outcome is left unspecified.

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% and the schema itself supplies the id format with an example ('bm-pozemok-mokrance'). The description only restates 'by id', adding no new meaning about format, casing, or whether slugs are accepted.

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 ('Returns one published listing by id') and explicitly names the returned payload (listing v1 schema plus public_url). An agent can distinguish it from search_listings by the single-id lookup, though the description never names the sibling.

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 implied by the 'by id' lookup and the word 'published', which signals that unpublished entries will not be returned. There is no explicit when-to-use versus search_listings or list_categories, and no stated failure condition for an unknown or unpublished 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