Fetch detailed information for a Google Maps place using its place_id, including address, coordinates, and business details. Limited to 1 request per second.
Google Maps place details API. Returns detailed information for a specified place_id. Rate limit is enforced at 1 request per second.
| Name | Required | Description | Default |
|---|---|---|---|
| place_id | Yes | Google Place ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description bears full burden. It only discloses the rate limit (1 req/s) but does not mention authentication requirements, output format, or that it is a read-only operation. This is insufficient for full behavioral transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is concise with two sentences: first states purpose, second adds rate limit. No unnecessary information. Perfectly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description is adequate but could be improved by explaining what 'detailed information' includes or any prerequisites. It covers the basics but lacks completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'place_id' has a description in the schema ('Google Place ID'), achieving 100% coverage. The tool description does not add additional meaning beyond what the schema already provides, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it returns detailed information for a specified place_id. The verb 'returns' and resource 'place details' are specific. However, it does not distinguish from sibling tools like google_map_search, but the purpose is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives such as google_map_search or geocoding. Only mentions a rate limit, which is not usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.