Skip to main content
Glama
Sign In

Kora

by io.github.onboardly-workspace
OverviewDiscussionsAdmin

Which inburgering exam do I need?

which_exam
Read-onlyIdempotent

Explains which inburgering exams belong to a situation the user chose themselves from the official list (their DUO or municipality letter is the authority). Without an id: the list. With an id: the exams, who runs them, why, and official sources. It works from the situation the user picks and needs no details about their background or residence status.

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

Input Schema

NameRequiredDescriptionDefault
situationNoA situation id from the list, or a short description like 'naturalisation'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds real value on top: it warns that the DUO or municipality letter is the authority, and it discloses what a lookup returns (exams, who runs them, why, official sources). It doesn't discuss error behavior for an invalid or unknown situation id.

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?

Three sentences, each carrying distinct information: purpose, the two operational modes, and the no-PII constraint. The mode behavior is front-loaded and there is no padding.

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 simple read-only lookup with one optional parameter and no output schema, the description covers both branches, the trust caveat, and the shape of results. Only the handling of an unrecognized situation value is left unstated.

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 coverage is 100%, so the schema already documents the single optional 'situation' parameter. The description reinforces the origin of the value ('from the official list') and the optionality, but adds little syntax or format meaning beyond the schema's own example.

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 and resource: it 'explains which inburgering exams belong to a situation,' and it distinguishes its two modes (list vs. exam detail). It does not explicitly contrast itself with siblings like inburgering_help or knm_facts, so the agent must infer that this is the exam-selection tool.

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

Usage Guidelines4/5

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

Gives explicit conditional guidance: 'Without an id: the list. With an id: the exams...' plus a clear constraint that it 'needs no details about their background or residence status,' which stops the agent from over-collecting user info. No alternative tools are named for cases this one doesn't cover.

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

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