Skip to main content
Glama
Sign In
rijschool-mcp

rijschool-mcp

by RibbaBV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Provincies

provincies

Retrieve data for all twelve Dutch provinces, including the number of driving schools, average pass rate, average lesson price, and largest cities.

Instructions

De twaalf provincies met het aantal rijscholen, het gemiddelde slagingspercentage, de gemiddelde prijs per les en de grootste steden.

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": "provincies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It states what data is returned (the twelve provinces with listed attributes) but does not disclose potential limitations, error conditions, or whether the output is a fixed list. It is transparent about the content but lacks details on behavior in edge cases.

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?

The description is a single, concise sentence that immediately states the subject (the twelve provinces) and the key associated data. No unnecessary words or repetition.

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?

The description provides enough context for an agent to understand the tool's purpose and the data it returns, even without an output schema. It specifies the exact attributes included for each province, though it omits details about the exact format or data types.

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?

There are no parameters, and the schema description coverage is effectively 100%. The baseline for parameter semantics is therefore 3, and the description adds no additional parameter-related information because none exists.

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 clearly states the tool provides the twelve provinces with specific accompanying data (number of driving schools, average pass rate, average price per lesson, largest cities). It is specific and distinguishes itself from sibling tools that focus on individual driving schools, prices, or cities.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention any conditions or typical use cases, leaving the agent to infer applicability solely from the purpose.

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

Deploy Server

Other Tools