Skip to main content
Glama

VN GroundTruth

motorbike_rules

Read-only

Penalties in Vietnam for riding a motorbike without a valid license, or with a foreign license / 1968-Convention IDP but no national license (Decree 168/2024, Art. 18). Includes legal basis and source.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "motorbike_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
activityNooptional filter, e.g. 'IDP'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: the jurisdiction, the exact legal instrument cited (Decree 168/2024, Art. 18), and that responses include legal basis and source, which tells the agent how authoritative the answer is. It does not state how current the content is beyond the decree number, but for a static reference tool this is solid.

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?

One sentence states the scope and scenario, followed by a short clause on what is returned; nothing is redundant. The jurisdiction and legal citation are front-loaded where they matter most.

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

Completeness4/5

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

For a one-optional-parameter, read-only lookup with no output schema, the description covers what the tool answers and what the answer includes (legal basis and source). The main residual gap is whether results are limited to motorbikes or extend to other vehicle classes, but overall it is complete enough to call correctly.

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 optional 'activity' parameter is documented there as a filter with an example ('IDP'). The description never mentions the parameter, though its enumeration of scenarios (no license, foreign license, IDP) hints at what values filter meaningfully. Baseline 3 applies since the schema does the heavy lifting.

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?

The description names a precise resource and scope: penalties in Vietnam for riding without a valid license, or with a foreign license/1968-Convention IDP but no national license, anchored to Decree 168/2024, Art. 18. An agent can immediately tell this is a static legal-reference lookup rather than an enforcement or entry check. It does not explicitly contrast itself with siblings, but their topics (entry, disruptions, evisa domains, quotas) are far enough apart that confusion is unlikely.

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

Usage Guidelines3/5

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

Usage is implied by the narrow scope: consult it when a question concerns motorbike license penalties in Vietnam. There is no explicit when-to-use/when-not-to-use statement, no mention of prerequisites (e.g., that it answers a hypothetical rather than checking a specific traveler's case), and no pointer to alternatives such as check_entry for entry requirements.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources