AutoIsto — car watch

Search cars AutoIsto offers today

intent_search_offers

Read-onlyIdempotent

Use this when the user wants to find a used car for sale in Slovakia now. Pass what they are looking for as one short phrase (Slovak or Czech works best), e.g. "škoda octavia kombi do 12000 eur". Returns up to 20 cars from AutoIsto's offer in AutoIsto's own order, each with a link to the car on www.autoisto.sk, plus what was understood, which words were not applied and what had to be relaxed. When suggestIntent is true (nothing or little found, or part of the phrase was dropped), offer the user intent_publish_intent with the same statement so AutoIsto keeps watching. Results come from listings AutoIsto aggregates from the Slovak market and may be incomplete; no seller contact is returned.

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": {
      "statement": "<statement>"
    },
    "name": "intent_search_offers"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	At most this many cars (default 10; AutoIsto returns at most 10).
`statement`	Yes	What the user is looking for, e.g. "suv automat do 25000 €".

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already mark this as read-only, idempotent, non-destructive, and not open-world. The description adds substantial context beyond that: result ordering, links, understood/dropped/relaxed phrase reporting, suggestIntent behavior, incomplete aggregate listings, and no seller contact returned.

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?

The description is front-loaded with the primary use case and then layers on return behavior and fallback guidance. Every sentence carries operational information; there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description explains the return shape: up to 20 cars, AutoIsto order, links, interpretation details, and limitations. Combined with annotations covering safety, the definition is complete enough for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description still adds meaningful semantics for statement by recommending one short phrase, noting Slovak or Czech works best, and giving a concrete example beyond the schema's own example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it is used to find a used car for sale in Slovakia now. It also describes the scope and result set, including up to 20 cars from AutoIsto's offer, so an agent can distinguish it from sibling intent tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use the tool: when the user wants to find a used car for sale in Slovakia now. It also names the alternative path by telling the agent to offer intent_publish_intent when suggestIntent is true, covering the key when-to-use and fallback scenario.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AutoIsto — car watch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?