Skip to main content
Glama
gander-tools

OpenStreetMap Tagging Schema MCP Server

by gander-tools

Get Tag Values

get_tag_values

Retrieve all documented values for any OpenStreetMap tag key, with localized display names. Ideal for discovering tag options like amenity types, learning proper terminology, or building UI selection lists.

Instructions

Retrieve all possible values for a specific OpenStreetMap tag key, with localized human-readable names for both the key and each value. This tool searches through the OSM tagging schema (both predefined field options and preset definitions) to find every documented value that can be used with the specified key. Returns four pieces of information: the normalized key name, localized key display name, a simple array of all values, and a detailed array with localized names for each value. Use this to discover what values are available for a tag (e.g., all amenity types), learn the proper terminology for values, or build UI selection lists. Essential for understanding OSM's controlled vocabularies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagKeyYesThe OpenStreetMap tag key to retrieve values for (e.g., 'amenity', 'building', 'highway', 'natural', 'shop'). Supports both simple keys and namespaced keys with colons (e.g., 'addr:street', 'name:en'). The tool will search both field definitions and preset tags to find all documented values. Case-sensitive, use lowercase for standard OSM keys.
optionsNoOptions to control query output: 'limit' restricts the maximum number of values returned (useful for tags with many values like 'name').
Behavior4/5

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

With no annotations, the description fully discloses the search mechanism (through OSM tagging schema, field options, and preset definitions) and the return structure (four pieces of info), but does not mention rate limits, authentication needs, or any side effects, though the tool is read-only.

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?

The description is three sentences, each serving a distinct purpose: main action, search scope, return structure, and use cases. No unnecessary words.

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 no output schema, the description explains the return format (four pieces, arrays with localized names) and usage examples, but could be slightly more precise about the data types and structure of the detailed array.

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?

The input schema covers 100% of parameters with good descriptions, and the description adds value by explaining the purpose of tagKey (e.g., examples) and options.limit (max results for performance), though the schema already provides adequate detail.

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 verb 'retrieve' and resource 'possible values for a specific OpenStreetMap tag key', and distinguishes from sibling tools like search_tags and get_preset_details by focusing on value retrieval rather than searching or presets.

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?

The description explains when to use the tool (discover values, learn terminology, build UI lists) but does not explicitly state when not to use it or mention alternatives, though the context implies other tools for searching or validating.

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/gander-tools/osm-tagging-schema-mcp'

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