Skip to main content
Glama

Search pages

search_pages
Read-onlyIdempotent

Search the public pages on OnMap.me: local businesses in the United States and unofficial pages for public places (parks, libraries, public offices, museums, stations, landmarks, sports venues). Returns name, kind, city, a one-line summary and the page address. Use get_page for the full facts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or state to narrow to, for example "Dallas" or "TX".
limitNoHow many results (default 10).
queryNoWords to look for in the name, kind, place or summary, for example "library" or "white rock".
categoryNoKind of page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent behavior, so the description does not need to restate safety. It adds useful context by specifying that only public pages are searched and listing the exact fields returned, though it omits details like result ordering or pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tight sentences with no wasted wording. Scope and return fields are front-loaded, and the alternative tool is named at the end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description sufficiently explains the return values and the search scope. All four optional parameters are fully documented in the schema, and the relationship to get_page is clear, so an agent has what it needs to invoke the tool correctly.

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 all four parameters thoroughly. The description adds no extra parameter semantics beyond what the schema provides, which is appropriate given the high coverage.

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?

The description gives a specific verb and resource ('Search the public pages on OnMap.me') and immediately scopes what pages are searchable, including concrete examples of page types. It clearly distinguishes itself from get_page by noting that the search returns only name, kind, city, summary, and address, while get_page provides full facts.

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?

It explicitly directs the agent to use get_page for full facts, which is a clear alternative and condition. However, it does not state exclusions such as when not to search or whether private/non-public pages exist, leaving a small gap in usage guidance.

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.