Skip to main content
Glama
Sign In
aka-recht

aka-recht

by Cehha79
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

journal lesen

journal_lesen
Read-only

Reads a case's chronological journal from JOURNAL.md, returning entries oldest to newest so you can review the full history of a legal matter.

Instructions

Verlauf eines Falls aus JOURNAL.md, neueste Einträge zuletzt.

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": {
      "fall": "<fall>"
    },
    "name": "journal_lesen"
  }
}

Input Schema

NameRequiredDescriptionDefault
fallYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond annotations: the data source is JOURNAL.md and entries are returned oldest-to-newest-last. It does not say what happens if no journal exists for the case.

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?

A single front-loaded sentence with zero filler; the data source and ordering constraint are both stated compactly and nothing is repeated from the schema or annotations.

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

Completeness3/5

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

For a simple single-parameter read tool with annotations covering safety and no output schema, the description is close to adequate. Gaps remain on the 'fall' identifier format and on behavior when the journal is missing or very large, which the schema and annotations do not cover.

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 0% for the single 'fall' parameter. The description implies 'fall' selects which case's journal to read ('Verlauf eines Falls'), which adds some meaning, but gives no format hint (case ID vs. name) to compensate for the undocumented schema.

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?

Names a specific verb+resource: reading a case's history from JOURNAL.md, plus the ordering of results. The read counterpart to the sibling journal_schreiben is inferable from the name, but the description does not explicitly distinguish itself from other case-reading siblings like fall_uebersicht.

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

Usage Guidelines2/5

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

No statement of when to use this versus fall_uebersicht, dokument_text, or any other read tool, and no prerequisites (e.g., journal must exist). Usage is only implied by the name and the mention of JOURNAL.md.

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

Deploy Server

Other Tools