Skip to main content
Glama

NS Pros MCP Gateway

google-maps__resolve_maps_urls

Resolves a list of Google Maps URLs into canonical Google Maps Place IDs.

When to call this tool (CRITICAL):

Input Requirements (CRITICAL):

  • **urls (arr

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": {
      "urls": "<urls>"
    },
    "name": "google-maps__resolve_maps_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesRequired. The Google Maps URLs to be resolved. Each URL should be a valid Google Maps URL, for example, https://maps.app.goo.gl/..., https://www.google.com/maps/place/..., or https://maps.google.com/.... Currently, only URLs pointing to a single place are supported. You may specify up to 20 URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the 20-URL batch cap and the 'single place only' limitation, but says nothing about failure handling for unresolvable or expired short links, rate limits, or whether results come back in input order.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The front-loaded purpose and bolded section headers are good structure, but the text is cut off mid-sentence at '**`urls` (arr', leaving a dangling Input Requirements section. The URL format examples are also repeated verbatim between the usage section and the schema, which is wasted space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter lookup tool this covers purpose, trigger, batch limit, and the single-place restriction, and the phrase 'extract the underlying canonical Place IDs' hints at the return. However, with no output schema, the truncated input section and the absence of any statement about return shape or partial failures leave gaps.

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?

There is only one parameter and schema coverage is 100%, so the schema already documents it fully. The description restates the same URL examples and batch limit rather than adding new meaning such as per-URL error semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource pair: resolve Google Maps URLs into canonical Place IDs, with example URL forms. It does not distinguish itself from the similarly named sibling resolve_names, so an agent must infer the difference from the name alone.

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 'When to call this tool' section gives a concrete trigger (user supplies a Maps sharing link) and enumerates the URL shapes that qualify. It stops short of stating when NOT to use it or naming an alternative for name-based lookups, which is what a 5 would require.

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.