Skip to main content
Glama
Sign In
german-archives-mcp

german-archives-mcp

by ianderso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cache_status

Read-only

Report this session's requests by host and cache use without making network calls.

Instructions

Report this session's requests, by host, and cache use. Makes no network call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cache_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, and 'Makes no network call' largely restates openWorldHint=false. The one genuine addition is the data scope: the report covers only the current session, not historical or persisted data. It says nothing about cost, aggregation level, or output format.

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, zero filler, with the scope and content of the report front-loaded before the clarifying constraint. Every clause earns its place.

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 parameterless diagnostic tool with no output schema, the description conveys the essentials: what is reported (requests by host, cache use) and that it is local-only. It could be slightly more complete by indicating what 'cache use' contains (e.g. hits/misses) since no output schema documents the return shape.

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?

The tool takes zero parameters, so the baseline is 4 and the empty schema leaves nothing for the description to compensate for. No parameter meaning is needed or expected here.

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?

Specific verb plus resource: 'Report this session's requests, by host, and cache use.' The scope ('this session's') is stated, and the sibling tools (ddb_*, hessen_*, labw_* searches and image lookups) are clearly unrelated data sources, so no differentiation is required. Only 'cache use' remains slightly abstract about which metrics are reported.

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?

There is no explicit when-to-use guidance and no alternatives are named; usage is only implied by 'Makes no network call,' which suggests it is a cheap, safe diagnostic call. With zero parameters and no competing sibling, the practical risk of misselection is low, so implied guidance is adequate but not exemplary.

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