Skip to main content
Glama
Sign In

ARN Konsumenttvist

by io.github.hawaleska
OverviewDiscussionsAdmin

Hämta ARN-beslut

arn_get_decision

Hämta hela texten från ett ARN-beslut genom att ange ärendenummer, exempelvis 2022-17895. Anropet kan förbruka en fri användning, även vid upprepning.

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": {
      "case_number": "<case_number>"
    },
    "name": "arn_get_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false and idempotentHint=false without explaining why, and the description fills that gap by warning that the call may consume a free usage "även vid upprepning" (even on repetition). That quota/repeat-cost warning is valuable behavioral context an agent would otherwise not have and is consistent with the non-idempotent annotation.

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 short sentences carrying only the essential facts: what is returned, which identifier to supply, and the cost caveat. The cost warning is appropriately placed at the end so the action itself is front-loaded.

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 single-parameter fetch tool with no output schema, the description covers the operation, the input format, and the important quota side effect. What is missing is failure behavior (e.g., unknown case number) and a pointer to the search tools for locating a case number.

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 0% and the schema only labels the field "Case Number", so the description's example format "2022-17895" is the main source of parameter meaning. It stops at one example, leaving questions about accepted formatting, leading zeros, or case-sensitivity unanswered.

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?

The description names a specific verb and resource ("Hämta hela texten från ett ARN-beslut") and specifies the input (ärendenummer), which clearly separates a full-text fetch from the search siblings. It does not explicitly name arn_search or arn_search_and_read as the alternatives, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

Usage is implied: the agent should call this when it already has a case number, and the example "2022-17895" illustrates the expected input. There is no explicit when-not guidance or pointer to arn_search for discovering a case number in the first place.

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

All ARN Konsumenttvist 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