Dayze MCP

Dayze Contacts

get_people

Read-only

Retrieve the authenticated user's private Dayze contacts, listing avatar and photo counts. Optionally include notes and control pagination with limit and offset.

Instructions

List the authenticated user's Dayze Contacts (private CRM; table people). Each contact includes avatar_url, photo_count, and has_photos; use get_person_photos(person_id) for the full gallery. Notes omitted by default (has_notes flag); pass include_notes=true for progressive fetch (credential/secret spans are redacted server-side). Supports limit (default 100, max 500) and offset; returns total and truncated. Distinct from public notable People at /people. Advertised name get_people is stable; tools/call also accepts get_contacts / list_contacts. Requires OAuth or a supported scoped credential. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size (default 100, max 500)
`cursor`	No
`offset`	No	Skip N rows (default 0)
`include_notes`	No	When true, include notes (server-redacted). Default false.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	Yes
`total`	Yes
`offset`	Yes
`people`	Yes
`has_more`	No
`ordering`	No
`truncated`	Yes
`expires_at`	No
`next_cursor`	No
`server_time`	No
`snapshot_at`	No
`snapshot_id`	No
`include_notes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.28.0Sep 16, 2026

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

addedInput schema / properties / include_notes

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

addedInput schema / properties / limit

Added value: +{
+  "description": "Page size (default 100, max 500)",
+  "type": "number"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip N rows (default 0)",
+  "type": "number"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "expires_at": {
+      "type": "string"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "include_notes": {
+      "type": "boolean"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "next_cursor": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "offset": {
+      "type": "number"
+    },
+    "ordering": {
+      "type": "string"
+    },
+    "people": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze person or contact record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "server_time": {
+      "type": "string"
+    },
+    "snapshot_at": {
+      "type": "string"
+    },
+    "snapshot_id": {
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "people",
+    "total",
+    "limit",
+    "offset",
+    "truncated"
+  ],
+  "type": "object"
+}

First observedv1.6.2Jul 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses OAuth/scoped credential requirements, server-side redaction of credential/secret spans, pagination behavior (limit/offset, total, truncated), and stable alias names. None of these contradict the annotations, and they add substantial operational context.

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?

The description is dense and front-loaded with the core purpose and primary alternative. Every sentence carries useful information, though the block crams many distinct details (aliases, auth, pricing, redaction, pagination) together. It is appropriately sized but slightly encyclopedic.

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?

Given the output schema and annotations, the description covers intent, filtering, pagination, auth, and naming alternatives well. The main gap is cursor-based pagination: the schema exposes a cursor parameter but neither it nor the description explains how cursor interacts with offset/limit.

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?

With 75% schema coverage, the schema already documents limit, offset, and include_notes. The description adds value by giving default/max values, explaining progressive-fetch semantics for include_notes, and noting redaction. However, the cursor parameter is undocumented in both the schema and description, preventing a perfect score.

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 action ('List') on a specific resource (the authenticated user's Dayze Contacts, table people). It explicitly distinguishes itself from public notable People at /people and from get_person_photos, so an agent can tell it apart from siblings without opening schemas.

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?

It gives clear when-to-use guidance: use get_person_photos(person_id) for the full gallery, pass include_notes=true for progressive fetch, and avoid confusing this with public notable People. It also mentions supported aliases and authentication requirements, leaving little ambiguity about invocation context.

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

Deploy Server