GermanExam.pro

Look up exam rubric

lookup_exam_rubric

Read-onlyIdempotent

Use this when the user wants to know how the writing section of a German C1 exam is assessed: the criteria with their weights, the level or grade scale, the passing rule and the expected text length for TestDaF, DSH, Goethe-Zertifikat C1, telc Deutsch C1 Hochschule or telc Deutsch C1 (general). Read-only reference data based on the published exam rubrics (the result says where a breakdown per criterion is our own); no sign-in needed. This is the scale only and grades nothing: when the user wants their text assessed, call evaluate_text instead of estimating points, criterion marks or a level from this rubric yourself. Not for other languages or exams.

Input Schema

Name	Required	Description	Default
`exam`	Yes	Which exam: testdaf, dsh, goethe_c1, telc_c1 (telc Deutsch C1 Hochschule) or telc_c1_allgemein (telc Deutsch C1, general).

Output Schema

Name	Required	Description	Default
`reference`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026
- removedOutput schema / properties / reference / properties / formats / items / properties / originNote / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / reference / properties / formats / items / properties / originNote / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / reference / properties / formats / items / properties / recommendedMinWords / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / reference / properties / formats / items / properties / recommendedMinWords / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / reference / properties / passRuleEn / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / reference / properties / passRuleEn / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedOct 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world behavior, and the description still adds real context: the data is drawn from published exam rubrics, the result flags where a per-criterion breakdown is the provider's own, and no sign-in is needed. It stops short of describing result shape, but an output schema exists so that burden is lifted.

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

Conciseness4/5

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

The trigger condition and scope are front-loaded and every sentence carries information: coverage, provenance, read-only status, exclusion, and the sibling hand-off. The prose is dense and slightly run-on, but there is no filler to cut.

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

Completeness5/5

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

With only one enum parameter, a full output schema, and rich annotations, the description supplies everything left: scope, provenance, auth expectation, exclusions, and the hand-off to evaluate_text. An agent can select and call this correctly without further information.

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% and the enum already documents each exam identifier, so the baseline is 3. The description corroborates the exam list and adds the useful constraint that only the writing section rubric is returned, but contributes no syntax or format detail beyond the schema.

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?

Names a specific verb (look up) and resource (exam rubric) and narrows it precisely to the writing section of German C1 exams, listing the five exams covered. It is unmistakably distinct from evaluate_text, which it explicitly names as the grading counterpart.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when the user wants to know how the writing section ... is assessed'), an explicit alternative with its selecting condition ('when the user wants their text assessed, call evaluate_text instead of estimating points'), and an explicit exclusion ('Not for other languages or exams'). Nothing is left to inference.

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

All GermanExam.pro tools Inspect

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

Need Help?