Dayze — Life Context

Life Graph Export

get_life_graph

Read-only

Explicit private life-graph export: favorites/VIP plus people with edges or recent event tags. Pass full=true for a larger capped list. Optional event–people links. Requires OAuth or a supported scoped credential. ($0.25; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`full`	No	Include additional people by last interaction, up to max_people
`max_people`	No
`event_links_limit`	No
`include_event_links`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hot`	Yes
`edges`	Yes
`nodes`	Yes
`edge_count`	Yes
`node_count`	Yes
`event_people_links`	No
`max_people_requested`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "edge_count": {
+      "type": "number"
+    },
+    "edges": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A relationship edge between people.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "event_people_links": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A recent event-to-person link.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "hot": {
+      "type": "boolean"
+    },
+    "max_people_requested": {
+      "type": "number"
+    },
+    "node_count": {
+      "type": "number"
+    },
+    "nodes": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze person or contact record.",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "hot",
+    "node_count",
+    "edge_count",
+    "nodes",
+    "edges"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 17, 2026

addedInput schema / properties / full

Added value: +{
+  "default": false,
+  "description": "Include additional people by last interaction, up to max_people",
+  "type": "boolean"
+}

changedInput schema / properties / max_people / default
```
Previous value: -150New value: +80
```

First observedJul 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to reassert safety. It adds valuable behavioral context by disclosing the private export scope, the cap behavior behind full=true, optional event-people links, the OAuth/scoped-credential requirement, and the $0.25 cost. This goes beyond what the annotations provide.

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 front-loaded: the first clause states what the tool exports, followed by the key flag, optional links, and auth/cost note. Every sentence earns its place, and there is no filler or redundant restatement of the tool name.

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, annotations, and the tool's simple parameter structure, the description covers essential invocation details: scope, the full flag, optional links, auth, and cost. The only notable gaps are explicit guidance around the max_people/event_links_limit caps and alternatives, but these are not critical for a successful call.

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?

With only 25% schema description coverage, the description must compensate for underdocumented parameters. It explicitly mentions full=true and 'Optional event-people links,' but it never names or explains max_people or event_links_limit, and 'larger capped list' is vague about the actual cap. This is only partial compensation for four parameters.

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 identifies the action ('export') and the object ('private life-graph'), and it enumerates the graph's contents: favorites/VIP plus people with edges or recent event tags. It does not explicitly contrast with sibling tools like get_life_context or get_people, but the name and content make the purpose distinguishable.

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 implies usage context through phrases like 'Explicit private life-graph export' and 'Pass full=true for a larger capped list,' and it states an authentication requirement. However, it never explicitly says when to choose this tool over related siblings such as get_people or get_life_context, nor does it state exclusions or alternatives.

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.