Asterwise

Vehicle Number Check

asterwise_check_vehicle_number

Read-onlyIdempotent

Strips non-digits from a vehicle registration token, reduces the numeric run to a single number, and returns the same harmony schema as mobile analysis.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — owner baseline. AFTER: None.

INPUT CONTRACT: Letters and separators are ignored; reduction uses numeric digits only. Owner name and birth date are optional and not used.

DO NOT CONFUSE WITH: asterwise_check_mobile_number — phone digit rules (national number, country code left out). asterwise_get_business_name_analysis — evaluates business Expression, not registration digits.

Full output and error contract: https://docs.asterwise.com/mcp/tools/check-vehicle-number/

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": {
      "vehicle_number": "<vehicle_number>"
    },
    "name": "asterwise_check_vehicle_number"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No	Not used: the analysis depends only on the digits. Omit it; it is accepted only so older calls keep working.
`name`	No	Not used: the analysis depends only on the digits. Omit it; it is accepted only so older calls keep working.
`vehicle_number`	Yes	Vehicle registration number, e.g. 'DL01AB1234'.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

changedInput schema / properties / date / description

Previous value: -"Date in YYYY-MM-DD format. Defaults to today when omitted."New value: +"Not used: the analysis depends only on the digits. Omit it; it is accepted only so older calls keep working."

changedInput schema / properties / name / description

Previous value: -"Person's full name as commonly written; letters are converted to numerology values."New value: +"Not used: the analysis depends only on the digits. Omit it; it is accepted only so older calls keep working."

Changed8 schema fields changedOct 4, 2026

addedInput schema / properties / date / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / date / default
```
Added value: +null
```

changedInput schema / properties / date / description

Previous value: -"Date in YYYY-MM-DD format."New value: +"Date in YYYY-MM-DD format. Defaults to today when omitted."

removedInput schema / properties / date / type
```
Removed value: -"string"
```

addedInput schema / properties / name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / name / default
```
Added value: +null
```
removedInput schema / properties / name / type
```
Removed value: -"string"
```

changedInput schema / required

Previous value: -[
-  "vehicle_number",
-  "name",
-  "date"
-]New value: +[
+  "vehicle_number"
+]

Changed1 schema field changedSep 7, 2026

changedInput schema / properties / date / description

Previous value: -"Date in YYYY-MM-DD format. Defaults to today when omitted."New value: +"Date in YYYY-MM-DD format."

Changed4 schema fields changedSep 5, 2026

addedInput schema / properties / date / description

Added value: +"Date in YYYY-MM-DD format. Defaults to today when omitted."

addedInput schema / properties / name / description

Added value: +"Person's full name as commonly written; letters are converted to numerology values."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

addedInput schema / properties / vehicle_number / description

Added value: +"Vehicle registration number, e.g. 'DL01AB1234'."

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```

changedInput schema / required

Previous value: -[
-  "vehicle_number",
-  "name",
-  "date",
-  "response_format"
-]New value: +[
+  "vehicle_number",
+  "name",
+  "date"
+]

First observedApr 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real behavioral detail beyond them: the digit-stripping/reduction algorithm and the input contract that letters and separators are ignored. It does not address failure modes, but points to the docs for the error contract.

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-loaded with the core behavior and then cleanly sectioned into WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE WITH, which is easy to scan. The closing documentation URL is useful but slightly padding, keeping it short of a 5.

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, so return values need not be explained, and the description only needs to state the shape (same harmony schema as mobile analysis). Combined with the named prerequisite, the disambiguation rules, and the error-contract link, nothing an agent needs to invoke 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%, so the schema already documents vehicle_number, date, name, and response_format. The description's INPUT CONTRACT reiterates that name/date are optional and unused, which matches the schema text rather than adding new meaning, so 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?

The description states a precise verb chain (strips non-digits, reduces numeric run, returns harmony schema) against a specific resource (vehicle registration token). It explicitly distinguishes itself from asterwise_check_mobile_number and asterwise_get_business_name_analysis, so an agent can route without opening any schema.

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?

The WORKFLOW block names a recommended prerequisite (asterwise_get_numerology_profile) and explicitly states AFTER: None, and the DO NOT CONFUSE WITH section names two concrete alternatives with the distinguishing rule for each. Both when-to-use and when-not are covered explicitly.

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

All Asterwise tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?