Skip to main content
Glama
Sign In
osm-mcp

osm-mcp

by a-tsitanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

run_sql

Run read-only SQL queries on OpenStreetMap PostGIS tables to retrieve geographic features and perform spatial analysis.

Instructions

Run a single read-only SELECT/WITH query against the OSM tables.

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": {
      "sql_text": "<sql_text>"
    },
    "name": "run_sql"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNo
sql_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It specifies read-only and single query, but lacks details on authentication, error handling, rate limits, output format, or behavior on invalid queries.

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?

Single sentence efficiently front-loads key info (read-only, SELECT/WITH). Could be improved with structured details but is not verbose.

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?

Given the complexity of a general SQL tool and no output schema, the description omits critical details like error handling, result limits, and handling of large queries. The sibling tools list is available but not leveraged.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description does not explain the parameters. 'sql_text' is implied to be a SQL query but no format or placeholder info; 'params' is not mentioned at all.

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 runs a single read-only SELECT/WITH query against OSM tables. This is a specific verb+resource and distinguishes it from sibling tools like search_features or count_by_category which are more specific.

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 versus alternatives. The description implies it's for arbitrary SQL queries not covered by siblings, but does not mention when not to use it or recommend specific alternatives.

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