AutoIsto — 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 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 aggregates from the market, so they cover only cars listed on AutoIsto 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?

Adds substantial context beyond the readOnly/idempotent annotations: a hard cap of 20 newest matches, the fact that these mirror the emails the user receives, that the server cannot post into the conversation itself, and that results are market-aggregated, possibly incomplete, and may include already-sold cars. These are exactly the behavioral caveats an agent needs before summarizing results.

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 usage trigger and prerequisite, then the result shape, then the caveats — a sensible ordering. Some sentences are long and pack multiple claims (email parity + no chat messaging), but each carries information an agent would otherwise get wrong.

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?

Even though an output schema exists, the description still covers the things the schema would not: prerequisite state, result cap, provenance limits and staleness. Nothing an agent needs to call it and set user expectations 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 coverage is 100% and both parameters are already documented. The description restates intentCode as required and since as an ISO time returning only newer matches, which largely duplicates the schema rather than adding new semantics; 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?

States a specific verb+resource ("list matches" for an intent) and anchors it to the sibling that creates the intent ("intent_publish_intent"), so the agent can distinguish it from intent_get_intent/intent_publish_intent without opening a schema. The scope (cars AutoIsto found for a watch) is unambiguous.

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 created with intent_publish_intent") plus a state precondition ("Before the user confirms the intent there are no matches"). It does not explicitly route the agent away from intent_get_intent for related lookups, so the alternatives story is incomplete.

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?