Dayze — Life Context

Premium Notable Pack

notable_pack_premium

Read-only

S-tier guaranteed pack (score≥85, timeline≥8, image, embedding). Errors if below bar. Use when you need high-quality, complete notable context. Example slug: elon-musk. ($0.10)

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No
`slug`	Yes	Person slug, e.g. elon-musk
`peers`	No
`similar`	No

Output Schema

TableJSON Schema

Name	Required	Description
`profile`	No	Quality-gated public notable-person profile.
`quality`	No	Pack quality signals.
`timeline`	No
`life_in_days`	No	Age and current day-number calculations.
`birthday_peers`	No
`similar_people`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "birthday_peers": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "life_in_days": {
+      "additionalProperties": true,
+      "description": "Age and current day-number calculations.",
+      "type": "object"
+    },
+    "profile": {
+      "additionalProperties": true,
+      "description": "Quality-gated public notable-person profile.",
+      "type": "object"
+    },
+    "quality": {
+      "additionalProperties": true,
+      "description": "Pack quality signals.",
+      "type": "object"
+    },
+    "similar_people": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "timeline": {
+      "items": {
+        "additionalProperties": true,
+        "description": "Timeline item with a day number.",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavioral details: guaranteed quality thresholds, error behavior when the quality bar is not met, and a $0.10 cost. This goes well beyond the annotations and gives the agent a concrete contract for expected behavior.

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 compact and front-loads the most important guarantee, followed by error behavior, usage guidance, an example, and cost. Every fragment adds useful information, though the telegraphic style and slight redundancy between 'S-tier guaranteed' and 'high-quality' prevent a perfect score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose, quality bar, error behavior, cost, and an example slug, and an output schema is present. However, key optional parameters ('date', 'peers', 'similar') are unexplained, which leaves gaps for an agent trying to use the tool beyond its simplest invocation.

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?

Schema description coverage is only 25%, with only 'slug' documented in the schema. The description repeats the slug example (elon-musk) but provides no meaning for 'date', 'peers', or 'similar', leaving the agent to guess their purpose. Given the low schema coverage, the description should have compensated for these undocumented 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 resource as a premium notable pack with explicit quality guarantees: score≥85, timeline≥8, image, and embedding. It distinguishes this tool from sibling tools like notable_pack by emphasizing the S-tier guarantee and 'Errors if below bar', though it lacks an explicit action verb such as 'retrieves' or 'gets'.

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?

It explicitly states when to use the tool: 'Use when you need high-quality, complete notable context.' It provides clear context but does not name alternatives or specify when not to use it, despite sibling tools like notable_pack and notable_search existing.

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.