pifini

Get place details + reviews

get_place

Read-onlyIdempotent

Full details for one place by slug, including its most recent published reviews if any exist. listing_type distinguishes a curated entry from an unreviewed directory listing (see search_places) — recent_reviews is often an empty array, which means no reviews yet, not a low-quality place. Use the slug from search_places.

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": {
      "slug": "<slug>"
    },
    "name": "get_place"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Place slug from search_places

Output Schema

Name	Required	Description	Default
`url`	No
`city`	No
`name`	No
`slug`	No
`type`	No
`address`	No
`country`	No
`summary`	No
`website`	No
`category`	No
`avg_rating`	No
`price_tier`	No
`description`	No
`is_verified`	No
`is_sponsored`	No
`listing_type`	No
`review_count`	No
`recent_reviews`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

addedOutput schema / properties / recent_reviews / items / properties / verification_basis

Added value: +{
+  "description": "How the reviewer's visit was established. ticket_scan and transaction are strong evidence, rsvp and geo_checkin are weaker, manual is self-declared and none is an unverified opinion. Describe the review accordingly.",
+  "enum": [
+    "ticket_scan",
+    "transaction",
+    "rsvp",
+    "geo_checkin",
+    "manual",
+    "none"
+  ],
+  "type": "string"
+}

Changed1 schema field changedAug 5, 2026

addedOutput schema / properties / recent_reviews / items

Added value: +{
+  "properties": {
+    "body": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "date": {
+      "type": "string"
+    },
+    "rating": {
+      "type": "number"
+    },
+    "title": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verified_attendee": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "rating",
+    "verified_attendee",
+    "date"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 28, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "avg_rating": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "category": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "city": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "country": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "is_sponsored": {
+      "type": "boolean"
+    },
+    "is_verified": {
+      "type": "boolean"
+    },
+    "listing_type": {
+      "enum": [
+        "curated",
+        "directory"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "price_tier": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "recent_reviews": {
+      "type": "array"
+    },
+    "review_count": {
+      "type": "number"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "summary": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "type": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "website": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedJul 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it explains that recent_reviews may be an empty array meaning no reviews yet (not a low-quality place), and that listing_type distinguishes curated vs. directory entries. This goes beyond the annotations and helps interpretation.

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 concise sentences with no filler. The core purpose is front-loaded, and the important caveat about empty recent_reviews is included. Every sentence earns its place.

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?

For a simple single-parameter tool with an output schema, the description covers the essential usage: how to get the slug, what the response contains, and how to interpret a key field. No critical information is missing. The output schema handles return structure, so description need not duplicate that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the slug parameter is already documented. The description adds a meaningful hint about the parameter's origin ('Use the slug from search_places'), which is not in the schema and helps the agent correctly obtain the input. This is a value-add beyond the schema.

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 clearly states the tool returns full details for one place by slug, including recent reviews. It distinguishes this from search tools by referencing search_places for slug acquisition and explaining listing_type, though it doesn't explicitly name a sibling alternative like get_event. The verb-resource pairing is specific.

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?

The description provides the source for the required slug ('Use the slug from search_places') and clarifies the meaning of an empty recent_reviews array. However, it does not explicitly state when to use this tool vs. alternatives (e.g., when you have a slug and need details, use this rather than search_places). The guidance is implied but not fully explicit.

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

All pifini tools Inspect

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

Need Help?