Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_places_search

Search Google Maps businesses by query and location to retrieve names, addresses, phones, websites, ratings, and Maps links, with read-only results up to 60.

Instructions

Search businesses on Google Maps by kind and place (e.g. query 'clínicas', location 'Córdoba, Argentina'). Returns name, address, phone, website, rating and a Maps link. Read-only; up to 60 results.

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": {
      "query": "<query>"
    },
    "name": "kernel_places_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20)
queryYesWhat to look for, e.g. 'clínicas', 'estudios contables'
locationNoCity or area, e.g. 'Córdoba, Argentina'
radius_kmNoNot used by text search yet; keep the location precise instead

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description does useful work by declaring 'Read-only' and the 'up to 60 results' cap, which frames pagination and safety expectations. It still omits auth/permission requirements, behavior when location is omitted, and what the 60-result cap implies for a caller requesting a larger limit.

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?

Two tight sentences: purpose and example first, then return fields and the read-only/result-cap caveats. Every clause carries information, with only minor redundancy between the example and the schema's own query example.

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?

Because there is no output schema, listing the returned fields (name, address, phone, website, rating, Maps link) is genuinely necessary and is done. For a four-parameter read tool this is nearly complete; only sibling disambiguation and handling of the result cap are missing.

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 all four parameters are already documented, including the caveat that radius_km is unused by text search. The description only restates the query/location pairing with an example, adding little beyond the schema baseline.

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 — 'Search businesses on Google Maps by kind and place' — with a concrete query/location example, so the agent knows exactly what the tool retrieves. It does not differentiate itself from siblings such as kernel_places_near or kernel_places_list, so the agent must infer that this is the free-text variant.

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 through the example ('clínicas' in 'Córdoba, Argentina'), which shows the intended text-search pattern. There is no explicit statement of when to choose this over nearby or list-based place tools, and no note about when a location is required versus optional.

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