Dayze — Life Context

List Places

get_places

Read-only

Known venues: visit-graph places plus saved place cards (saved_places from business_contacts) with address, opening_hours, and affordability ($/$$/$$$). query filters both lists by name. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No
`area`	No
`city`	No
`near`	No	Filter saved cards by area/tag/notes (e.g. Madeira).
`limit`	No
`query`	No	Name contains, case-insensitive (e.g. "QA Map Probe Tokyo").
`country`	No
`affordability`	No	$ \| $$ \| $$$

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes
`places`	No
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`saved_count`	No
`inspect_note`	No	How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.
`saved_places`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 29, 2026

addedOutput schema / properties / account

Added value: +{
+  "additionalProperties": false,
+  "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
+  "properties": {
+    "display_name": {
+      "description": "Account display name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "handle": {
+      "description": "Account handle, e.g. @goh.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "description": "How to disclose the account to the user.",
+      "type": "string"
+    },
+    "qa_fixture": {
+      "description": "True for a known QA test account: its records are fixture data, not a real life.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "handle",
+    "display_name",
+    "qa_fixture",
+    "note"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / inspect_note

Added value: +{
+  "description": "How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.",
+  "type": "string"
+}

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / query

Added value: +{
+  "description": "Name contains, case-insensitive (e.g. \"QA Map Probe Tokyo\").",
+  "type": "string"
+}

Changed6 schema fields changedSep 12, 2026

addedInput schema / properties / affordability

Added value: +{
+  "description": "$ | $$ | $$$",
+  "type": "string"
+}

addedInput schema / properties / area
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / near

Added value: +{
+  "description": "Filter saved cards by area/tag/notes (e.g. Madeira).",
+  "type": "string"
+}

addedInput schema / properties / tag
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / saved_count
```
Added value: +{
+  "type": "number"
+}
```

addedOutput schema / properties / saved_places

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "description": "Saved place card (business_contacts).",
+    "type": "object"
+  },
+  "type": "array"
+}

AddedSep 1, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false, closed world), so the bar is lower, and the description adds real operational context: an API key is required and each call costs $0.10. It also discloses the dual-source nature of the result. Missing only details like pagination or default limits.

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?

It is a compact two-clause construction that front-loads what is returned, then the filter and cost/auth caveats. The dense backticked token notation is slightly cryptic, but there is no filler.

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

Completeness3/5

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

An output schema exists so return values need not be explained, and auth/cost are covered. However, for an 8-parameter listing tool with 38% schema coverage, the ambiguity among the several overlapping geo/tag filters (near vs area vs tag vs city vs country) leaves the definition short of complete.

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

Parameters2/5

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

Schema coverage is only 38%, so the description must carry more of the load, yet it only clarifies `query` (filters both lists by name) and echoes affordability ($/$$/$$$). Filters like tag, area, city, near, limit, and country are undocumented in both places, so the agent cannot distinguish their semantics.

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 resource and scope: it returns known venues merged from the visit-graph `places` list and saved place cards (`saved_places`), plus the fields returned. That is clearer than a tautology, but it doesn't name or contrast with siblings like get_place, search, or get_place_visits, leaving the agent to infer the distinction.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no alternatives named. The only usage-adjacent statement is that `query` filters both lists, which is parameter behavior, not selection guidance. With dozens of get/search/place siblings available, the agent gets no help choosing this one.

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

All Dayze — Life Context 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.