Skip to main content
Glama

Read a page

get_page
Read-onlyIdempotent

The full content of one OnMap.me page as markdown (hours, address, phone, prices, questions and answers, guides), with where the facts come from. For an unofficial page it also gives the place's official site, the day the facts were last checked there, and the source pages.

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": {
      "handle": "<handle>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe page's handle, for example "klyde-warren-park" (the part after onmap.me/@).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the payload is markdown, facts are attributed to sources, and unofficial pages additionally return the official site, a last-verified date, and source pages.

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 sentences, front-loaded with the primary payload, then the conditional extras for unofficial pages. The parenthetical content list is dense but every item earns its place by telling the agent what to expect.

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?

With no output schema, the description must carry the return-shape burden, which it does by describing markdown output, source attribution, and the conditional extra fields. The only mild gap is that 'unofficial page' is not defined, but the distinction is clear enough to act on.

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?

There is a single parameter with 100% schema description coverage, including a concrete example handle, so the schema does the work. The description adds nothing about the handle beyond format, which is already covered, making the baseline 3 appropriate.

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 names a specific resource ('one OnMap.me page') and enumerates exactly what it contains (hours, address, phone, prices, Q&A, guides) delivered as markdown. It implicitly separates itself from get_guide by scoping to a single page's full content, though it never names a sibling directly.

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 the tool for pulling a single page's full content when the handle is known. There is no explicit when-to-use versus search_pages/check_handle guidance and no stated prerequisites or exclusions.

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.