Skip to main content
Glama

구글 지도 장소 검색

google_maps_search
Read-only

Google Maps place search: return up to 20 places (name, address, phone, rating, reviews, hours, coordinates) for a keyword. 키워드의 구글 지도 장소(상호·주소·전화·평점·리뷰 수·영업시간·좌표)를 최대 20곳 조회합니다. 처리에 보통 30~60초, 느리면 85초까지 걸립니다. [호출당 15포인트]

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": {
      "keyword": "<keyword>"
    },
    "name": "google_maps_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes장소 검색어 (예: 강남역 카페, 1~200자)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-web scope are covered. The description adds genuinely useful non-schema behavior: typical 30–60s latency, worst case 85s, and a cost of 15 points per call, which lets an agent budget and avoid redundant retries. It does not describe pagination or what happens when fewer than 20 places match.

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 content is front-loaded correctly, but every sentence is duplicated verbatim in Korean and English, roughly doubling length without adding information. Latency and cost details sit at the tail where they are easy to skim past.

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?

For a one-parameter read-only search with no output schema, the description covers result fields, result cap, latency, and cost — enough for an agent to call it correctly and set expectations. The absence of output schema makes a brief note on result ordering or empty-result behavior the only real gap.

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% for the single 'keyword' parameter, already documented as a 1–200 character place query with an example. The description adds no syntax, formatting, or regional/language hints beyond that, so the schema does the heavy lifting and 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 description gives a specific verb and resource ('Google Maps place search') and enumerates exactly what comes back (name, address, phone, rating, reviews, hours, coordinates) capped at 20 results per keyword. It is clearly distinguishable from youtube_search or amazon_product by resource, but it never names the closest siblings (google_search, location) to sharpen the boundary.

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?

Usage is only implied: an agent can infer this is for local/business lookups by keyword. There is no explicit 'use this when…' or 'use google_search instead when…' guidance, and no prerequisites (e.g., whether a location bias parameter exists) are stated.

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.