get_vehicle_import_rulesTemporary admission rules for a foreign-plated vehicle in one country: allowed days, per entry or per window, carnet requirement, green card. A country without a rule we can stand behind returns nothing rather than a guess.
| Name | Required | Description | Default |
|---|---|---|---|
| country | Yes | Country: ISO alpha-2 code, slug or zone code, e.g. georgia or GE. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds meaningful open-world behavior beyond the annotations: for a country with no reliable rule, the tool 'returns nothing rather than a guess.' This enriches the readOnlyHint and openWorldHint without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler: the first defines the tool's scope and content, the second covers the empty-result edge case. Both sentences earn their place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter, read-only lookup with no output schema, the description lists the returned rule categories and states the no-rule behavior. Combined with the input schema and annotations, an agent has enough context to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the country parameter with format examples at 100% coverage. The description only restates 'one country' and adds no new parameter-level detail, so it remains at the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the resource precisely: temporary admission/import rules for a foreign-plated vehicle in one country, and lists the key rule categories (allowed days, per-entry/per-window, carnet, green card). This clearly distinguishes it from sibling visa, fuel, and event tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The domain and scope ('foreign-plated vehicle in one country') make the intended use clear and separate it from the visa-rule siblings. However, it does not explicitly name an alternative tool or say when not to use this one.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose targeting specific resources like fuel prices, events, weather, or stories, with no overlap in functionality. For example, compare_fuel_prices and find_cheapest_fuel serve different comparison and search roles, while get_fuel_prices provides detailed data, making misselection unlikely.
All tool names follow a consistent verb_noun pattern (e.g., compare_fuel_prices, get_currency_rate, list_events), using snake_case throughout. This predictability aids agents in understanding and selecting tools without confusion from mixed conventions.
With 11 tools, the count is well-scoped for the vanlife travel domain, covering key areas like fuel, events, weather, and stories. Each tool earns its place by addressing distinct needs, avoiding bloat while providing comprehensive coverage for planning and information retrieval.
The tool set offers strong coverage for vanlife travel, including fuel price comparison, event listings, weather suitability, and story searches, with no dead ends. A minor gap exists in lacking update or delete operations for user-specific data, but core informational and planning workflows are fully supported.