Opencages

Geocode

geocode

Read-onlyIdempotent

Forward-geocode an address or place name to latitude/longitude using OpenCage (requires API key); supports country-code filtering, bounding box, and language; returns coordinates and structured address components.

Input Schema

TableJSON Schema

Name	Required	Description
`abbrv`	No
`limit`	No
`query`	Yes
`bounds`	No	sw_lon,sw_lat,ne_lon,ne_lat
`language`	No
`countrycode`	No	Comma-sep ISO-3166-1 alpha-2 codes.
`no_annotations`	No

Output Schema

TableJSON Schema

Name	Required	Description
`rate`	No	Rate limit information
`status`	No	API response status
`results`	No	Array of geocoding results
`total_results`	No	Total number of results found

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "Paris, France"
+  },
+  {
+    "countrycode": "US",
+    "limit": 5,
+    "query": "1600 Pennsylvania Avenue"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Response from OpenCage forward geocoding API",
+  "properties": {
+    "rate": {
+      "description": "Rate limit information",
+      "properties": {
+        "limit": {
+          "description": "Request limit",
+          "type": "integer"
+        },
+        "remaining": {
+          "description": "Remaining requests",
+          "type": "integer"
+        },
+        "reset": {
+          "description": "Reset timestamp",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "results": {
+      "description": "Array of geocoding results",
+      "items": {
+        "properties": {
+          "annotations": {
+            "description": "Additional annotations (if no_annotations not set)",
+            "type": "object"
+          },
+          "bounds": {
+            "description": "Bounding box coordinates",
+            "type": "object"
+          },
+          "components": {
+            "description": "Address components breakdown",
+            "type": "object"
+          },
+          "confidence": {
+            "description": "Confidence score 0-10",
+            "type": "integer"
+          },
+          "formatted": {
+            "description": "Formatted address string",
+            "type": "string"
+          },
+          "geometry": {
+            "description": "Geographic coordinates",
+            "properties": {
+              "lat": {
+                "description": "Latitude",
+                "type": "number"
+              },
+              "lng": {
+                "description": "Longitude",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "API response status",
+      "properties": {
+        "code": {
+          "description": "HTTP status code",
+          "type": "integer"
+        },
+        "message": {
+          "description": "Status message",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "total_results": {
+      "description": "Total number of results found",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds context beyond annotations: mentions external API dependency (OpenCage), authentication requirement (API key), and return types (coordinates and structured address components). No contradiction with annotations.

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?

Single sentence efficiently conveys the tool's purpose, prerequisite, and key features. Front-loaded with the main action, no wasted 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 an output schema exists (as per context signals), the description appropriately omits return value details. However, it could mention rate limits or authentication setup alongside the API key requirement. Overall, sufficiently complete for a geocoding tool.

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

Parameters2/5

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

Schema description coverage is low (29%), with only bounds and countrycode having descriptions. The description broadly mentions supported filters but does not detail each parameter's meaning or format. Many parameters (abbrv, limit, language, no_annotations) lack clarification, and the description does not compensate adequately.

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 action ('Forward-geocode'), the resource ('address or place name to latitude/longitude'), and the data source ('OpenCage'). It differentiates from sibling tools like 'reverse' by specifying forward geocoding.

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 states a prerequisite ('requires API key') and lists supported features (country-code filtering, bounding box, language). It implies when to use this tool but does not explicitly exclude alternatives or provide when-not-to-use guidance.

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

All Opencages tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.