Skip to main content
Glama

bakom_broadband_coverage

Read-onlyIdempotent

Check broadband coverage at a Swiss location by entering coordinates and minimum download speed. Returns coverage percentage and available technologies (DSL, cable, fiber).

Instructions

Breitbandversorgung (Festnetz) für einen Standort in der Schweiz abfragen.

Zeigt, ob ein Gebäude am angegebenen Standort mit einer bestimmten Downloadgeschwindigkeit versorgt wird. Nutzt den BAKOM Breitbandatlas via geo.admin.ch API (Rasterauflösung: 250×250 Meter).

Args: params (BroadbandCoverageInput): Eingabeparameter mit: - latitude (float): Breitengrad WGS84 (45.8–47.9) - longitude (float): Längengrad WGS84 (5.9–10.6) - min_speed_mbps (str): Mindestgeschwindigkeit ('30','100','300','500','1000') - response_format (str): 'markdown' oder 'json'

Returns: str: Breitbandverfügbarkeit mit Abdeckungsprozentsatz und verfügbaren Technologien (DSL, Kabel, Glasfaser).

Schema: { "standort": {"lat": float, "lon": float}, "geschwindigkeit_mbps": int, "abdeckung_prozent": float, "glasfaser_verfuegbar": bool, "technologien": list[str], "datenquelle": str }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already provide readOnlyHint=true and idempotentHint=true. The description adds valuable behavioral context: uses geo.admin.ch API with 250×250m raster, returns coverage percentage and technologies, and includes the output schema. Does not contradict annotations.

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 concise and well-structured: purpose sentence, API source, parameter list, and return schema. Front-loaded with the core action. Slight redundancy in Args section but overall efficient.

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?

Given the tool's moderate complexity (4 parameters, nested input) and presence of output schema, the description explains geographical bounds, speed options, technologies, and data source. Lacks error handling or example usage but is sufficiently complete for a straightforward query tool.

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?

The input schema provides comprehensive descriptions for all parameters, including ranges and enum values. The description's Args section repeats this info, adding little extra beyond what the schema already offers. Baseline 3 is appropriate given high schema coverage.

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 the tool queries fixed-network broadband coverage for a location in Switzerland, using specific verb 'abfragen' and resource 'Breitbandversorgung'. It distinguishes from siblings like mobilfunk_abdeckung (mobile) and glasfaser_verfuegbarkeit (glass fiber) by specifying 'Festnetz' and the BAKOM source.

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 explicit guidance on when to use this tool vs alternatives. Sibling tools exist for mobile coverage and glass fiber, but the description does not mention exclusions or comparative context. Implied usage only from the tool name and subject.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malkreide/bakom-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server