Skip to main content
Glama

Asterwise

by com.asterwise.mcp
OverviewDiscussionsAdmin

Vehicle Number Check

asterwise_check_vehicle_number
Read-onlyIdempotent

Strips non-digits from a vehicle registration token, reduces the numeric run with owner name and birth date, 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.

DO NOT CONFUSE WITH: asterwise_check_mobile_number — phone digit rules including country codes. 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/

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format.
nameYesPerson's full name as commonly written; letters are converted to numerology values.
vehicle_numberYesVehicle registration number, e.g. 'DL01AB1234'.
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed4 schema fields changed
    • 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'."
  3. Changed2 schema fields changed
    • 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"
+]
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive, and the description adds meaningful behavior beyond that: letters and separators are ignored, only numeric digits are used, and owner name and birth date are combined in the reduction. The explicit input contract and link to the full output/error contract further disclose behavior.

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?

The description is well-structured with labeled sections like WORKFLOW, INPUT CONTRACT, and DO NOT CONFUSE WITH, and the core operation is front-loaded. There is minor redundancy between the first sentence and the INPUT CONTRACT about ignoring letters and separators, but no significant wasted content.

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?

With an output schema present and annotations covering the safety profile, the description supplies the processing rules, workflow context, sibling exclusions, and a link to the full output/error contract. An agent has enough information to select and invoke this tool correctly without needing additional inference.

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 description coverage is 100%, giving a baseline of 3, and the description adds value by clarifying vehicle_number processing: non-digits are stripped and only numeric digits participate in the reduction. It does not materially expand on the name or date parameters beyond what the schema already provides.

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 first sentence states a specific verb and resource: strips non-digits from a vehicle registration token, reduces the numeric run with owner name and birth date, and returns the same harmony schema as mobile analysis. The DO NOT CONFUSE WITH section explicitly separates it from mobile number and business name analysis 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?

The DO NOT CONFUSE WITH section names exact alternatives and their distinguishing conditions, such as phone digit rules including country codes for asterwise_check_mobile_number. The WORKFLOW block adds a recommended preceding tool, giving clear workflow context for when this tool fits.

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

All Asterwise toolsInspect
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