Dayze — Life Context

Person Neighborhood

get_person_neighborhood

Read-only

Subgraph around one user-owned person_id — profile (avatar_url, photo_count, has_photos) plus declared connections. Use get_person_photos for the full gallery. Notes omitted unless include_notes=true (redacted). Requires OAuth or a supported scoped credential. ($0.15; API key required)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`person_id`	Yes	UUID
`include_notes`	No	When true, include center.notes (server-redacted). Default false.

Output Schema

TableJSON Schema

Name	Required	Description
`center`	Yes	A Dayze person or contact record.
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`connections`	Yes
`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.
`include_notes`	No
`connection_count`	Yes

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 1, 2026
- addedOutput schema / properties / include_notes
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedAug 31, 2026

addedInput schema / properties / include_notes

Added value: +{
+  "description": "When true, include center.notes (server-redacted). Default false.",
+  "type": "boolean"
+}

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "center": {
+      "additionalProperties": true,
+      "description": "A Dayze person or contact record.",
+      "type": "object"
+    },
+    "connection_count": {
+      "type": "number"
+    },
+    "connections": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A declared connection to the center person.",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "center",
+    "connection_count",
+    "connections"
+  ],
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/non-destructive, and the description adds genuinely new behavioral context: notes are omitted and redacted unless include_notes=true, and it requires OAuth or a supported scoped credential. It also surfaces a per-call cost of $0.15, which annotations do not convey.

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 dense but front-loaded set of sentences that leads with the core behavior and uses the alternative, credential, and cost notes as trailing qualifiers. No sentence is filler, though the parenthetical stacking (profile fields, redaction, pricing) makes it slightly crowded.

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, return values need no explanation, and the description covers the alternative tool, credential requirement, cost, and notes behavior. A reader still lacks any hint about graph size or scope limits of the neighborhood, which is a minor gap for a subgraph-returning read.

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 both parameters including the server-redaction behavior of include_notes. The description's restatement of the notes toggle adds little beyond what the schema provides, so the 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?

The description states a specific verb+resource (a subgraph around one person_id) and enumerates what is returned (profile fields avatar_url, photo_count, has_photos plus declared connections). It explicitly distinguishes itself from get_person_photos, so an agent can tell the two apart without opening a schema.

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 routes the agent to get_person_photos for the full gallery, giving a concrete alternative with a selecting condition. It does not spell out explicit when-not-to-use cases or prerequisites beyond credential requirements, so it falls short of the fully explicit bar.

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.