Skip to main content
Glama
Sign In
skkg-mcp

skkg-mcp

by kintopp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

skkg_guide

skkg_guide
Read-onlyIdempotent

Read topic-based guidance before searching SKKG to choose German search terms and understand IDs, rights, provenance, caveats, and citation practices.

Instructions

How to search SKKG well; read it before your first search, one topic at a time. Topics: overview, search_in_german, ids, rights_and_privacy, provenance, data_caveats, citing, other_sources. Start with overview, then read the topics the question needs; each result names the others.

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": "skkg_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoTopic to read: overview (Overview), search_in_german (Search in German), ids (Ids), rights_and_privacy (Rights and privacy), provenance (Provenance), data_caveats (Data caveats), citing (Citing), other_sources (Other sources). Default overviewoverview

Output Schema

NameRequiredDescriptionDefault
textYesThe topic's guidance, in Markdown
titleYes
topicYes
topicsYesEvery topic, in order, to pass as `topic`

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral facts: output is chunked per topic, over-fetching is discouraged, and each result self-references the remaining topics so the agent can navigate without re-guessing names. It stops short of saying how large or structured each topic's content is.

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?

Front-loaded imperative clause followed by the topic inventory and the reading order, with no filler. The topic list mildly duplicates the enum but earns its place by making the definition self-contained.

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?

With an output schema present and 100% parameter coverage, the description only needs to explain calling discipline and topic selection, which it does. The one gap is that it does not characterize what a topic's content covers or how the agent should behave if a topic proves insufficient.

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% and the enum documents every topic with a label, so the schema already carries the baseline. The description adds selection semantics beyond the enum: start with overview, then pull only the topics the question requires, which is operational advice the schema cannot express.

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?

Clear guide-reading tool with enumerated topics.

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

Usage Guidelines5/5

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

Explicit timing ("read it before your first search"), explicit calling discipline ("one topic at a time"), and explicit sequencing ("Start with overview, then read the topics the question needs"). An agent knows exactly when to invoke it and in what order without further inference.

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