Dayze MCP

Person Neighborhood

get_person_neighborhood

Read-only

Fetch a person's profile and declared connections by person_id, including avatar, photo count, and photo availability. Optionally include notes.

Instructions

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.
`connections`	Yes
`include_notes`	No
`connection_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.28.0Sep 16, 2026

addedInput schema / properties / include_notes

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

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"
+    },
+    "include_notes": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "center",
+    "connection_count",
+    "connections"
+  ],
+  "type": "object"
+}

First observedv1.6.2Jul 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description adds meaningful behavioral context: notes are redacted and omitted unless include_notes=true, an OAuth or supported scoped credential is required, and an API key is needed. It also clarifies the returned data scope and does not contradict the annotations.

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 compact and well-structured: function is front-loaded, the alternative is named, notes behavior is clarified, and auth/pricing are included. No sentence is wasted and it remains easy to scan.

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?

Given the tool has an output schema, the description does not need to explain return values. It covers the person_id scoping, the include_notes behavior, authentication requirements, and the distinction from a sibling. Nothing essential is missing for correct selection and invocation.

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 baseline is a 3. The description adds extra meaning by specifying person_id must be user-owned and by explaining include_notes affects whether redacted notes are returned. These details go beyond the raw schema.

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 clearly states the tool returns a subgraph around one user-owned person_id, including profile fields and declared connections. It also differentiates from the sibling get_person_photos by directing that tool for the full gallery, leaving no ambiguity about scope.

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?

The description explicitly says 'Use get_person_photos for the full gallery,' which tells the agent when not to use this tool and which alternative to choose. It also clarifies authentication requirements and pricing, giving enough context for appropriate selection.

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

Deploy Server