Dayze — Life Context

Resolve Contact

resolve_person

Read-only

Resolve a nickname or surface name to a Dayze Contacts row via person_aliases → exact name → slug → unique substring. Returns avatar_url, photo_count, has_photos, and photos[{url,is_primary}] preview; use get_person_photos for full gallery. With financial_details:read, net_worth_assessment has the same sourced fields as the Contacts card; context-only evidence carries no personal number. Notes omitted unless include_notes=true (redacted). Prefer this before money or relationship tools when the agent only has a nickname. Advertised name resolve_person is stable; tools/call also accepts resolve_contact. ($0.05; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Nickname or display name to resolve
`query`	No	Alias for name
`include_notes`	No	Include redacted notes (default false)

Output Schema

TableJSON Schema

Name	Required	Description
`query`	No
`person`	No
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`aliases`	No
`resolved`	No
`candidates`	No
`matched_via`	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.

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"
+}

AddedAug 31, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already establish the safe read profile (readOnlyHint, destructiveHint=false, closed world), and the description adds substantial non-obvious behavior: the financial_details:read scope requirement, that context-only evidence carries no personal number, that notes are omitted/redacted unless include_notes=true, the $0.05 cost, and API-key requirement. It also discloses the resolve_contact alias accepted at tools/call, which is operationally important.

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?

Front-loads the core purpose and resolution chain, then layers return preview, auth scope, notes behavior, routing advice, alias, and cost. Dense but every clause carries distinct information; only slight compression loss from packing cost/alias into the same block.

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?

With an output schema present, return values need not be explained, yet the description still previews the key fields (avatar_url, photo_count, has_photos, photos[]). Combined with auth scope, redaction rules, cost, and sibling routing, an agent has everything needed to call it correctly.

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 3; the description goes beyond by clarifying the redaction semantics of include_notes and the alias behavior of name/query ('nickname or surface name to resolve'). This adds meaning about what the parameters actually trigger, though it does not explain the query-vs-name precedence.

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?

States a precise verb+resource ('Resolve a nickname or surface name to a Dayze Contacts row') and even spells out the resolution precedence chain (aliases → exact name → slug → unique substring). It differentiates from siblings by naming get_person_photos as the full-gallery alternative and by scoping the tool to the nickname case, so an agent can distinguish it from get_people or get_person_connections.

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?

Explicitly routes usage: 'Prefer this before money or relationship tools when the agent only has a nickname,' and points to get_person_photos for the full gallery. It gives clear positive context but no explicit when-not (e.g., what to use when you already have a stable person id), so it falls just short of full alternative coverage.

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.