AutoIsto CZ — car watch

Get the state of a car watch

intent_get_intent

Read-onlyIdempotent

Use this to check whether an intent created with intent_publish_intent is already confirmed by the user and active, waiting, expired or withdrawn. Requires the intentCode; returns the statement and dates only — never the user's e-mail, the hidden limit or any other personal data.

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_get_intent"
  }
}

Input Schema

Name	Required	Description	Default
`intentCode`	Yes	The intentCode returned by intent_publish_intent.

Output Schema

Name	Required	Description
`buyBy`	No
`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.
`statement`	No
`niceToHave`	No
`validUntil`	No	Date (YYYY-MM-DD) until which the intent is watched (before confirmation: until the draft is deleted).
`activeSince`	No
`hasHiddenLimit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: the set of lifecycle states it can report and a privacy guarantee that only the statement and dates are returned, never e-mail, the hidden limit, or other personal data.

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?

Two sentences, front-loaded with the action and the state enumeration, followed by the input requirement and the return/privacy constraint. No filler and nothing repeated from the schema.

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?

For a single-parameter, idempotent read with an output schema, the description covers purpose, the trigger condition, the possible states, and the privacy boundary of the response. Since an output schema exists it need not enumerate return fields, and nothing an agent needs to call it 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%, and the single intentCode parameter is already documented as 'the intentCode returned by intent_publish_intent'. The description only restates that the code is required, adding no format, pattern, or sourcing detail beyond the schema, so the 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 (fetch the state of an intent) and enumerates the concrete states returned (confirmed/active, waiting, expired, withdrawn). It also names the sibling that creates the intent (intent_publish_intent), so an agent can place it in the lifecycle without opening another schema.

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?

Explicitly frames the use case: check whether an intent published via intent_publish_intent has been confirmed. That is clear context for when to call it, but it never names the remaining alternatives (intent_withdraw_intent, intent_list_matches) or states when not to use this tool, so it stops short of full when/when-not 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?