aria-mcp-affald-horsens

find_address

Search for a Horsens Kommune address to retrieve PerfectWaste candidates with addressID and displayName, enabling free-text resolution or disambiguation before collection queries.

Instructions

Search for a Horsens Kommune address and return PerfectWaste address candidates (each with an addressID and a displayName). Use this to resolve a free-text address string before calling next_collection or collection_calendar, or to disambiguate when multiple addresses match (e.g. Søndergade 1 in both 8700 and 8740). Returns up to 30 candidates ordered by relevance.

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

Input Schema

Name	Required	Description	Default
`query`	Yes	Address string to search for in Horsens Kommune (e.g. "Vestergade 5", "Søndergade 1, 8700 Horsens").

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations provided, but description discloses return format, limit of 30 candidates, and relevance ordering. Does not mention side effects or rate limits, but acceptable for a search tool.

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 sentences with no wasted words; first sentence states purpose, second gives usage guidance and example. Very efficient.

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

Completeness5/5

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

For a single-parameter search tool with no output schema and two siblings, the description covers input, output, limits, ordering, and usage context. Completely sufficient.

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 has 100% coverage with a description for the query parameter. The tool description adds context about search scope (Horsens Kommune) and disambiguation, enhancing meaning beyond schema.

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 clearly states it searches for a Horsens Kommune address and returns candidates with addressID and displayName. It differentiates from siblings by specifying this tool resolves addresses before using next_collection or collection_calendar.

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

Usage Guidelines4/5

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

Explicitly says to use before next_collection or collection_calendar, and to disambiguate multiple matches. Provides an example. Could mention when not to use, but context is clear.

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

Deploy Server