AutoIsto CZ — car watch

List cars found for a car watch

intent_list_matches

Read-onlyIdempotent

Use this when the user asks what AutoIsto has found for an intent created with intent_publish_intent. These are the same cars AutoIsto e-mails to the user; this server cannot send messages into the conversation by itself. Requires the intentCode; optional since (ISO time) returns only newer matches. Returns at most 20 newest matches with the price in CZK and AutoIsto price verdict at the time of the match and a link. Before the user confirms the intent there are no matches. Matches come from listings AutoIsto CZ aggregates from the market, so they cover only cars listed on AutoIsto CZ and may be incomplete; a car may already be sold.

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": {
      "intentCode": "<intentCode>"
    },
    "name": "intent_list_matches"
  }
}

Input Schema

Name	Required	Description	Default
`since`	No	Only matches found after this ISO time.
`intentCode`	Yes	The intentCode returned by intent_publish_intent.

Output Schema

Name	Required	Description
`more`	No	More matches exist than returned; call again with since.
`found`	Yes
`status`	No	awaiting_consent = the user has not confirmed on the AutoIsto page yet; awaiting_email_confirmation = the user filled in the page and must click the link in the e-mail; active = AutoIsto is watching; expired = the confirmation link, the buy-by date or the intent's validity ran out; withdrawn = cancelled.
`matches`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: caps results at 20 newest, states contents (price in CZK, verdict at match time, link), discloses that results come from AutoIsto CZ aggregation and may be incomplete or already sold, and clarifies the server cannot post into the conversation. These are exactly the caveats an agent needs to set user expectations.

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?

Front-loads the trigger and requirement, then layers caveats in a logical order. Slightly dense with several long sentences, but nearly every clause carries distinct information; only the e-mail/conversation remark is marginally tangential.

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?

An output schema exists, yet the description still usefully previews result fields and, more importantly, covers data-quality limitations (aggregated source, possible sold cars, empty before confirmation) that the schema cannot express. Nothing an agent needs to call or interpret this correctly is missing.

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 the schema already documents both intentCode and since. The description's 'Requires the intentCode; optional since (ISO time) returns only newer matches' largely restates that, adding little format or edge-case detail; baseline 3 applies.

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?

Clear specific verb+resource: lists car matches that AutoIsto found for a watch created via intent_publish_intent. It also names the sibling it depends on (intent_publish_intent) and, by describing matches rather than intent metadata, separates itself from intent_get_intent.

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?

Gives an explicit trigger ('when the user asks what AutoIsto has found for an intent') and a precondition ('before the user confirms the intent there are no matches'). It does not explicitly say when NOT to use it (e.g. use intent_get_intent for intent settings), so it stops short of full alternative routing.

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

All AutoIsto CZ — 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?