Dayze — Life Context

Get Conditions

get_conditions

Read-only

Private health conditions owned by the user, for subject_type self (default) or an explicitly resolved Dayze Contacts person_id. A person condition never appears in the user's self list. status: open (default), suspected, active, improving, resolved or all. condition_id returns recent check-ins and care items for the same subject. ($0.05; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`status`	No	open (default: every condition not resolved), one status, or all.
`person_id`	No	Owned contact id; required for person.
`condition_id`	No	One condition, with its recent check-ins and care items.
`subject_type`	No	self, or person with person_id.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes
`status`	No	The filter applied: open, a status, or all.
`condition`	No	A private condition with explicit subject_type/person_id, source and confirmation_status.
`person_id`	No
`conditions`	No
`subject_type`	No	self or person.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 3, 2026

addedInput schema / properties / person_id

Added value: +{
+  "description": "Owned contact id; required for person.",
+  "type": "string"
+}

addedInput schema / properties / subject_type

Added value: +{
+  "description": "self, or person with person_id.",
+  "enum": [
+    "self",
+    "person"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / condition / description

Previous value: -"An owner health condition: condition_id, name, status, confirmed, sensitivity, symptoms, body_area, started_on, resolved_on, tracking_focus, treatments, notes, latest_checkin."New value: +"A private condition with explicit subject_type/person_id, source and confirmation_status."

changedOutput schema / properties / conditions / items / description

Previous value: -"An owner health condition: condition_id, name, status, confirmed, sensitivity, symptoms, body_area, started_on, resolved_on, tracking_focus, treatments, notes, latest_checkin."New value: +"A private condition with explicit subject_type/person_id, source and confirmation_status."

addedOutput schema / properties / person_id

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / subject_type

Added value: +{
+  "description": "self or person.",
+  "type": "string"
+}

Changed2 schema fields changedOct 3, 2026

changedOutput schema / properties / condition / description

Previous value: -"A private health condition: condition_id, name, status, confirmed, symptoms, body_area, started_on, resolved_on, tracking_focus, treatments, notes, latest_checkin."New value: +"An owner health condition: condition_id, name, status, confirmed, sensitivity, symptoms, body_area, started_on, resolved_on, tracking_focus, treatments, notes, latest_checkin."

changedOutput schema / properties / conditions / items / description

Previous value: -"A private health condition: condition_id, name, status, confirmed, symptoms, body_area, started_on, resolved_on, tracking_focus, treatments, notes, latest_checkin."New value: +"An owner health condition: condition_id, name, status, confirmed, sensitivity, symptoms, body_area, started_on, resolved_on, tracking_focus, treatments, notes, latest_checkin."

AddedSep 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so safety is covered. The description adds valuable context beyond that: the privacy boundary ('Private health conditions'), the isolation guarantee between self and person lists, the default status behavior, and the cost/auth requirement ($0.05; API key required). It doesn't cover pagination or return shape, but that is a minor gap given the existing annotations.

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 but front-loaded, starting with the resource and scope. Every sentence carries information: scoping rule, status defaults, condition_id behavior, and cost/auth. It is a bit compressed, which slightly hurts readability, but there is no wasted filler.

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, the description doesn't need to explain return values. It covers the essential operational context: subject scoping, default status, the condition_id drill-down, and billing/auth. An agent can call this correctly. The only minor gap is pagination behavior for list results, which is not mentioned.

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 all four parameters including enums and defaults. The description reinforces the default for status and the subject_type/person_id pairing, which is useful but largely redundant. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb+resource: 'Private health conditions owned by the user'. It explains the subject scoping (self vs. person) and distinguishes the two lists ('A person condition never appears in the user's self list'). It doesn't name its sibling get_health_trends or get_sleep_summary explicitly, so it doesn't reach the highest level of sibling differentiation, but the scoping rule is a strong differentiator.

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?

Gives clear context: use for the user's own conditions by default, or for a Dayze Contacts person when explicitly resolved with person_id. It also explains that condition_id returns recent check-ins and care items for the same subject, which effectively tells an agent when to use this tool vs. a broader list. No explicit exclusion of an alternative sibling is given, so not a 5.

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.