Skip to main content
Glama
Sign In
google-maps-mcp-server

google-maps-mcp-server

by ettysekhon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_place_details

Retrieve detailed information about a place using its unique Place ID, including address, phone number, website, and opening hours.

Instructions

Get detailed information about a specific place using its Place ID. Returns address, phone number, website, opening hours, and other details.

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": {
      "place_id": "<place_id>"
    },
    "name": "get_place_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
place_idYesThe unique Place ID
fieldsNoSpecific fields to retrieve (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses read-only nature and return types, but doesn't mention authentication, rate limits, or error handling. Contradiction not applicable.

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, front-loaded with purpose. Could be restructured with bullets for readability, but current form is efficient.

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?

Adequate for a 2-param read tool with no output schema. Explains what it returns but lacks guidance on error scenarios or return format. No output schema to rely on.

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 has 100% description coverage for place_id and fields. Description adds no extra meaning or constraints beyond schema, e.g., valid field values or usage of fields parameter.

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?

Clearly states the tool gets detailed information about a specific place using its Place ID, listing return types (address, phone number, etc.). Distinguishes from sibling tools like search_places, which returns a list.

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?

Implies usage context: when you have a Place ID and need details. Does not explicitly state when not to use or provide alternatives, but context with sibling names suggests appropriate use cases.

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