Skip to main content
Glama
Sign In

TEHET

by ua.com.tehet.mcp
OverviewDiscussionsAdmin

Ukraine car insurance (OSCPV) price

get_oscpv_price
Read-only

Indicative Ukrainian motor insurance prices from manual vehicle details.

Input Schema

NameRequiredDescriptionDefault
placeYesНазва міста або точна мітка «Назва, Область» з candidates. Без номера авто, пошти чи телефону.
driverAgeYesВік наймолодшого водія в роках.
startDateNoДата YYYY-MM-DD: від учора до +90 днів. Перевіряється, але поки не впливає на орієнтовну ціну.
termMonthsYes
vehicleKindYes
vehicleTypeNoОбов’язковий відповідний підтип для truck/bus/trailer; для car/moto заборонений.
vehicleYearNo
enginePowerKwNoКВт лише для електричного car; замість engineCapacity, не разом.
engineCapacityNoОб’єм у см³: car 50–20000, moto 1–3000. Не передавайте для truck/bus/trailer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / place / pattern
      Removed value: -"^[\\p{L}\\p{M}0-9 .,'’ʼ()·-]+$"
    • removedInput schema / properties / startDate / pattern
      Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • removedInput schema / properties / termMonths / anyOf
      Removed value: -[
-  {
-    "const": 6,
-    "type": "number"
-  },
-  {
-    "const": 12,
-    "type": "number"
-  }
-]
    • addedInput schema / properties / termMonths / enum
      Added value: +[
+  6,
+  12
+]
    • addedInput schema / properties / termMonths / type
      Added value: +"integer"
    • changedInput schema / properties / vehicleYear / maximum
      Previous value: -9007199254740991New value: +2100
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The word 'Indicative' usefully signals these are estimates rather than binding quotes, but there is no mention of auth, rate limits, or how the conditional parameter rules gate a result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence is efficient and front-loaded, but at this length for a 9-parameter tool with interdependent conditional fields it reads as under-specification rather than disciplined conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Nine parameters, four required, three enums and several conditional rules, with no output schema and no return-value or error guidance in the description. An agent cannot tell from the text what a valid call produces or which field combinations are legal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the description contributes zero parameter information; everything meaningful (the vehicleType requirement for truck/bus/trailer and its prohibition for car/moto, the enginePowerKw-vs-engineCapacity exclusivity, the date-range constraint on startDate) lives only in the schema, and several parameters carry no schema description at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Indicative Ukrainian motor insurance prices' for OSCPV, which reads distinctly from the sibling get_green_card_price. 'from manual vehicle details' clarifies the input mode, but the description never explicitly names the alternative or pricing context, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use framing, no prerequisites, no mention of get_green_card_price or get_fuel_prices as alternatives. Nothing tells the agent when this tool is the right choice versus the other insurance/pricing sibling.

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

All TEHET 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