Skip to main content
Glama
Sign In

It Admin Courts

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Ruling

get_ruling
Read-onlyIdempotent

Read the full text of one Italian administrative-court ruling found with search_rulings: pass its case_key, file and schema as returned there. Returns the court, ECLI where present, and the ruling text (truncated at max_chars). Source: Giustizia Amministrativa.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "202601116_01.html",
      "schema": "tar_bs",
      "case_key": "202500842",
      "max_chars": 3000
    },
    "name": "get_ruling"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesFile name from search_rulings, e.g. "202611921_01.html"
schemaYesCourt code from search_rulings, e.g. "tar_rm" or "cds"
case_keyYesCase number (nrg) from search_rulings, e.g. "202604234"
max_charsNoCharacters of text to return (1000-60000, default 15000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely new context — what is returned (court, ECLI, ruling text), that text is truncated at max_chars, and the upstream source (Giustizia Amministrativa). It does not discuss error behavior when a case_key/file combination is invalid, which is the main remaining gap.

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?

Two tight sentences: the action and its provenance constraint come first, return contents second. No filler, and nothing an agent needs is buried.

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?

There is no output schema, so the description carries the burden of describing returns and it does: court, ECLI where present, truncated text, plus the data source. Combined with complete parameter documentation, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds a semantic constraint the schema does not: these values must be passed as returned from search_rulings, and it restates the max_chars truncation effect on output. That is real value beyond the field-level docs.

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?

Specific verb ('Read the full text') plus a precisely scoped resource ('one Italian administrative-court ruling'), and it explicitly ties itself to search_rulings as the discovery counterpart. An agent can immediately tell this fetches a single known ruling rather than searching for one.

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?

States the prerequisite workflow clearly: the ruling must first be found with search_rulings, and its case_key, file and schema should be passed through unchanged. It implies the single-item vs. search split without explicitly saying 'do not use this to find rulings', so it falls just short of full when/when-not guidance.

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

All It Admin Courts 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