Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

datasets_apple_maps_places_item

Read-only

Returns one stored Apple Maps place record by Apple place id (the numeric id or the external id starting with I), including category path, full address, coordinates, contact details, hours, rating and when it was first and last observed. Use this after datasets_apple_maps_places_search when you already have a place id.

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": {
      "place_id": "<place_id>"
    },
    "name": "datasets_apple_maps_places_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
place_idYesApple place id: the numeric id or the external id starting with I, e.g. 6435622567484707146.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Read-only/open-world behavior is already declared by annotations, so the description's contribution is the payload inventory (category path, address, coordinates, contact details, hours, rating) plus the observation-window concept ('first and last observed'), which signals these are snapshotted records with freshness semantics. It doesn't say what happens for an unknown or stale id, keeping it short of a 5.

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?

Two sentences: the first delivers the return contract, the second delivers the routing rule. No filler, and the record contents are front-loaded before the usage note.

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 an output schema present, the description doesn't need to detail return shape, and annotations cover safety; the field inventory plus the search-then-fetch workflow makes the definition self-sufficient for a single-parameter lookup. Only the failure mode for an invalid/unknown place id is unaddressed.

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 coverage is 100% and the schema description already explains 'the numeric id or the external id starting with I'. The description restates the same id format, adding no new syntax or edge-case guidance, so baseline 3 applies.

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?

States a specific verb and resource ('Returns one stored Apple Maps place record by Apple place id') and scopes it to a single record, which cleanly separates it from the sibling search/nearby/facets tools. The word 'stored' also distinguishes it from the live apple_maps_place sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use it: 'Use this after datasets_apple_maps_places_search when you already have a place id.' That is a concrete precondition plus a named alternative, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources