Skip to main content
Glama

NS Pros MCP Gateway

google-maps__resolve_names

Resolves a batch list of specific location queries (landmark names or exact addresses) into canonical Google Maps Place IDs.

Input Requirements (CRITICAL):

  1. queries (array of objects - MANDATORY): A list of location queries to resolve. You may specify up to 20 queries.

    • Each query object must have:

      • text (string - MANDATORY): The text query representing a specific place name or address to resolve.

        • Examples: `'Googleplex, Mountain Vie

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": {
      "queries": "<queries>"
    },
    "name": "google-maps__resolve_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesYesRequired. A list of location queries to be resolved. You may specify up to 20 queries.
regionCodeNoOptional. An optional region code to bias the resolution results. If specified, the resolution results will be biased towards the entities that are in or near the specified region. This should be a CLDR region code. For example, "US" or "CA". Including `location_bias` or `region_code` often provides better results by narrowing the search space. If both `location_bias` and `region_code` are specified, `location_bias` takes precedence over `region_code`.
locationBiasNoOptional. An optional region to bias the resolution results. If specified, the resolution results will be biased towards the entities that are closer to this region. Including `location_bias` or `region_code` often provides better results by narrowing the search space. If both `location_bias` and `region_code` are specified, `location_bias` takes precedence over `region_code`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly does not meet it. It discloses the 20-query batch cap, but that sentence is a verbatim restatement of the schema's own description, and nothing is said about what happens with unresolvable queries, whether results map one-to-one to inputs, cost/rate limits, or matching precision.

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 purpose statement is front-loaded and the bolded structure is scannable. However, the bulk of the text is an input-requirements section that duplicates a schema already at 100% coverage, and the text terminates mid-example, so the length is not justified by added value.

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 three-parameter batch lookup the description covers the input contract and names the return artifact (Place IDs), which is the minimum needed to call it. With no annotations and no output schema, it should still say how partial failures and unresolvable entries are reported, since an agent preparing an up-to-20-item batch needs to know how to align results.

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?

Schema description coverage is 100%, so the schema already documents queries, regionCode, and locationBias in detail — including the CLDR format and the precedence rule that locationBias overrides regionCode. The description's parameter section restates the schema rather than adding syntax, format, or interaction details, so the baseline of 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 gives a specific verb, resource, and output: 'Resolves a batch list of specific location queries ... into canonical Google Maps Place IDs.' It also narrows the acceptable input to landmark names and exact addresses, which implicitly separates it from a free-text place search. It does not name a sibling (e.g. search_places) explicitly, so the differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives real when-not guidance: 'General locations like a chain name (e.g. Starbucks) or a search query like "restaurants" are not supported.' That tells an agent when to avoid this tool, but it never names an alternative to use instead, and it gives no guidance on when to prefer this over resolve_maps_urls.

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.