ONYST RVG

Gegenstandswert, Streit- oder Verfahrenswert ermitteln

rvg_determine_value

Read-onlyIdempotent

Ermittelt den Gegenstandswert (Streitwert, Verfahrenswert) aus den Sachangaben. Rufe es bei „Welcher Gegenstandswert?“ und bevor du rechnest, wenn er fehlt — nie schätzen, Posten nie selbst addieren. Er ist die Bezugsgröße jeder Wertgebühr. Die Art (art) bestimmt die Pflichtfelder, z. B. eine Miet- oder Pachtsache als miete_41_gkg mit monatsbetrag.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "rvg_determine_value"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes	Die Art der Wertermittlung und ihre Sachangaben.

Output Schema

Name	Required	Description	Default
`fehler`	No
`ergebnis`	No
`hinweise`	No
`istBerechenbar`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds meaningful behavioral context beyond them: it should be used instead of estimating or manually summing items, and its result is the reference value for every value fee. It does not discuss failure behavior, but the output schema covers the return value.

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 four sentences, front-loads the purpose, then gives the usage trigger, rationale, and one key parameter hint. Every sentence earns its place and there is no redundant wording.

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?

Given the rich nested input schema and the existence of an output schema, the description is complete enough: it covers purpose, when to use the tool, and how 'art' drives required fields. It could go slightly further by explicitly tying the output to the fee calculation siblings, but no critical information for invoking it correctly is missing.

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 'art' property already enumerates all required fields for each calculation type. The description reinforces that 'art' controls the required fields and gives one example, 'miete_41_gkg mit monatsbetrag', but this repeats information already present in the schema rather than adding new meaning.

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 uses a specific verb, 'Ermittelt', and names the exact resource, 'Gegenstandswert (Streitwert, Verfahrenswert)', plus its source, 'aus den Sachangaben'. It distinguishes itself from the calculation siblings by positioning the result as the input to fee calculation: 'bevor du rechnest' and 'Bezugsgröße jeder Wertgebühr'.

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?

It gives a clear trigger for use: when the question is 'Welcher Gegenstandswert?' or when the value is missing before calculating. It also states a strong usage constraint, 'nie schätzen, Posten nie selbst addieren'. It does not explicitly name the sibling alternatives or state a when-not condition, which keeps it below a 5.

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

All ONYST RVG 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?