Skip to main content
Glama

Check service area

check_service_area
Read-onlyIdempotent

Check whether Sky Solar serves a German postcode. Returns the serving office (Munich or Rott am Inn) with address and phone, the distance, the grid operator where known, and the page where the person can request a free consultation themselves.

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": {
      "postcode": "<postcode>"
    },
    "name": "check_service_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage of the answer: de (German) or en (English).de
postcodeYesGerman postcode (Postleitzahl), five digits, e.g. 81829

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 genuine value by disclosing the response contents (office, address, phone, distance, grid operator, consultation URL) and the geographic scope limit (German postcodes only). It does not say what the answer looks like when the postcode is *not* served, which is the one behavioral gap left.

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?

A single sentence, no filler, with the core verb and scope front-loaded. It is slightly overloaded by the parenthetical office names and the trailing consultation-page clause, but every clause still carries practical information.

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?

With no output schema present, the description takes on the job of describing return values and does so concretely, in the absence of annotations gaps. For a simple two-parameter read tool, an agent has everything it needs to call it and interpret the result — only the negative-result shape is missing.

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 100%, with postcode pattern and example plus a locale enum fully documented, so the schema carries the semantics. The description only reinforces that the postcode is German; it says nothing about the locale parameter or how it changes output language, so it adds little beyond structured data.

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?

States a specific verb and resource ("Check whether Sky Solar serves a German postcode") and even enumerates what comes back: serving office, distance, grid operator, consultation page. No sibling tool covers service-area coverage, so an agent can select it without opening any schema.

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?

Usage is only implied — an agent infers it should call this to validate coverage before sizing or consultation steps. There is no explicit "use this when…" framing, no exclusion, and no routing to relevant siblings like consultation_link or size_system even though it mentions the consultation request page.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources