Dayze MCP

Notable Person Profile

notable_profile

Read-only

Retrieve a person's bio-only profile using their slug. Get just the biographical JSON, omitting life-in-days, similar people, and birthday peers.

Instructions

Bio-only profile JSON by slug (no life-in-days, similar, or birthday peers). Prefer notable_pack for “who is X / age in days / peers”. Example: taylor-swift. ($0.02)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Person slug, e.g. albert-einstein

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bio`	No
`name`	Yes
`slug`	Yes
`about`	No
`handle`	No
`sources`	No
`timeline`	No
`image_url`	No
`birth_date`	No
`death_date`	No
`occupation`	No
`profile_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.28.0Sep 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "about": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "bio": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "birth_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "death_date": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "handle": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "image_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": "string"
+    },
+    "occupation": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "profile_url": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "sources": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "timeline": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "slug",
+    "name",
+    "profile_url"
+  ],
+  "type": "object"
+}

First observedv1.6.2Jul 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it returns only bio data, excludes peer/life-in-days content, and costs $0.02. No contradiction with annotations is present.

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 entire description is compact and front-loaded: core behavior first, exclusions and routing second, then a concrete example and pricing. Every clause earns its place with no redundant filler.

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?

For a single-parameter read-only tool with an output schema and clear sibling routing, the description is complete. It tells the agent what the tool returns, what it excludes, when to use a different tool, and even cost. No critical context for correct invocation is missing.

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?

The schema already fully documents the single slug parameter with 100% coverage. The description reinforces that the lookup is by slug and provides a concrete example, but it does not add substantially new semantic information beyond the schema.

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 and resource: returning a bio-only profile JSON by slug. It explicitly differentiates itself from notable_pack by listing what it does not include (life-in-days, similar, birthday peers), so an agent can immediately understand its narrow purpose versus siblings.

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?

The description explicitly says to prefer notable_pack for 'who is X / age in days / peers', giving a clear when-not-to-use condition and naming the alternative. The slug-based lookup and example 'taylor-swift' further clarify the intended 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