Skip to main content
Glama

Keresés a piactéren

search_marketplace
Read-onlyIdempotent

Keresés a Kódvéna Piactér apróhirdetései között kulcsszóval, kategóriával, településsel. Linkeket ad a hirdetésekre.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_marketplace"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoMit keresel, pl. „kerékpár 28”
cityNoTelepülés (nem kötelező)
categoryNoKategória azonosítója (nem kötelező), pl. elektronika

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact - that results are links to the ads - but says nothing about result limits, pagination, ordering, or empty-result behavior.

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, front-loaded with the action and corpus, with the return hint appended. No filler, though the phrase is dense enough that a reader must parse multiple filter types in one clause.

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 simple, fully-documented, read-only search endpoint with no output schema, the definition covers what it searches and roughly what it returns. Remaining gaps - result count limits and behavior with zero filters - are minor for this complexity level.

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%, including examples for the query and category fields, so the schema carries the parameter semantics. The description's mention of keyword, category and settlement aligns with the three params but adds no format or precedence detail (e.g. whether filters AND together).

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 states a specific verb ("Keresés") and a specific resource ("Kódvéna Piactér apróhirdetései") plus the filter axes. It is clearly distinguishable from generic siblings like search or search_real_estate by naming the marketplace classifieds corpus, though it does not explicitly contrast with those siblings.

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: an agent can infer this is the tool for searching marketplace ads, but there is no explicit when-to-use/when-not guidance or routing to alternatives such as a general web search or real-estate search. It also does not say what happens when all optional filters are omitted.

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