Skip to main content
Glama
Sign In
kalundborg-mcp

kalundborg-mcp

by Parthee-Vijaya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search_content

Search all content on kalundborg.dk to find news, services, contact info, and popular pages for Kalundborg Municipality.

Instructions

Søg i alt indhold på kalundborg.dk

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": {
      "query": "<query>"
    },
    "name": "search_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSøgeord eller sætning at søge efter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention that the operation is read-only, what the response looks like, or any limitations. The bare 'search' implies safety but does not explicitly disclose behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, one sentence with no wasted words. It is structurally fine, though it essentially restates the tool's name in a different language, adding little extra value.

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

Completeness2/5

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

The tool has no output schema and no annotations, so the description should cover context like result format, scope, and relationship to sibling tools. It only provides a one-liner, lacking guidance on when to use it over search_services or how the results are returned.

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 100% as the only parameter 'query' is described ('Søgeord eller sætning at søge efter'). The description itself adds nothing about parameters, so the baseline of 3 applies.

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?

The description 'Søg i alt indhold på kalundborg.dk' clearly states a specific verb (search) and resource (all content on kalundborg.dk). It distinguishes from siblings like search_services by covering all content, not just a subset.

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 guidance is given on when to use this tool versus alternatives. There is no mention of exclusions (e.g., 'for services, use search_services') or any contextual hints beyond the bare description.

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