Live read-only search for verified campsites in Turkey. Book on kampyeri.org.
Scored across 2 tools
The two tools, 'search' and 'fetch', have clearly distinct purposes: search queries for campsites, while fetch retrieves details for a specific result. There is no overlap or ambiguity in their functionality.
Both tools are named with simple, lowercase action verbs ('search' and 'fetch'), maintaining a consistent and intuitive naming convention. No mixed styles or confusing prefixes.
With only two tools, the set is minimal but appropriate for a focused search-and-retrieve workflow. While below the typical 3-15 range, it covers the core needs without redundancy, making it slightly under but reasonable.
For a read-only campsite search service, the combination of search (to find results) and fetch (to retrieve detailed information) provides a complete workflow. No additional operations like create, update, or delete are needed for the stated purpose.
After search, call this with the result id (slug) to get summary, features, rating and the booking URL. url is always the canonical kampyeri.org page. Do not invent details.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Kamp yeri slug'ı (search sonucundaki id) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true (safe read), and the description adds return-content context (summary, features, rating, booking URL) plus the canonical-URL guarantee. No contradiction between description and annotations; it adds useful behavioral detail beyond the structured data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the key action ('After search, call this…'), and every clause earns its place — return contents, canonical URL note, and anti-hallucination constraint. Zero waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter fetch tool with readOnlyHint=true and no output schema, the description adequately covers what the tool returns and the required input. Could detail return formatting, but given the simplicity and annotations, this is complete enough.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% since the id parameter is fully documented as 'Kamp yeri slug'ı (search sonucundaki id)'. The description reinforces that id comes from search results but adds minimal new meaning beyond the schema, earning the baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb+resource pattern: 'call this with the result id (slug) to get summary, features, rating and the booking URL'. It clearly distinguishes from the sibling 'search' by explicitly stating 'After search', making the fetch/get-details purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
States exact timing ('After search'), the required input (result id/slug), and adds a valuable constraint ('Do not invent details') that prevents hallucination. This is explicit when-to-use guidance that complements the sibling tool sequencing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Use this whenever the user asks about camping, kamp, glamping, karavan, caravan, tent, campervan, or campsites in Turkey. Do not invent campsites. Call this tool first, then fetch for details. Returns at most 10 live results; each url is the canonical kampyeri.org booking page.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Doğal dil sorgusu, örn: 'İzmir denize sıfır karavan' |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the readOnlyHint and openWorldHint annotations, the description adds critical behavioral context: it warns against inventing campsites, caps results at 10, and clarifies that each URL is the canonical kampyeri.org booking page. This meaningfully helps the agent understand the tool's constraints and output semantics.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: it opens with the trigger condition, then gives the anti-hallucination guard, the workflow, and the result constraints. Every sentence adds value with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter search tool with no output schema, the description covers when to use it, the workflow, result count, and URL semantics. It could briefly mention what fields are returned in the results, but the guidance to fetch details afterward reduces the need for that.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides 100% coverage for the single 'query' parameter, including a natural-language example. The description does not add additional parameter-level meaning, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies a campsite search tool for Turkey, triggered by camping-related terms, and states that it returns live results with canonical booking-page URLs. It also distinguishes itself from the sibling 'fetch' tool by instructing to call search first, then fetch details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly lists when to use the tool ('whenever the user asks about camping, kamp, glamping, karavan, caravan, tent, campervan, or campsites in Turkey'), provides a workflow ('Call this tool first, then fetch for details'), and includes a guardrail ('Do not invent campsites'). This is clear, actionable guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
fetchsearchFind, price and book independent campsites with live availability; guests pay the campsite directly.
Campground search, live availability, weather, safety, and gear for 10,000+ US campgrounds.
Upcoming theatre, concerts, stand-up, exhibitions and festivals in Türkiye. Read-only, no sign-in.
Search Australian campsites, caravan parks and free camps; weather, gear, road trips and booking.
Add one secure layer between your agents and this server.
