Dayze — Life Context

Search Notable People

notable_search

Read-only

Search the public Dayze notable-people catalog by name, occupation, or slug. Use when you need to find a person before fetching a pack. Example slug: albert-einstein. ($0.01)

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Primary search query.
`limit`	No	Max results 1–20
`query`	No	Alias for q.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes	Number of matches returned.
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 29, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "limit": {
-        "default": 8,
-        "description": "Max results 1–20",
-        "type": "number"
-      },
-      "q": {
-        "description": "Primary search query.",
-        "type": "string"
-      },
-      "query": {
-        "description": "Alias for q.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "q"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "limit": {
-        "default": 8,
-        "description": "Max results 1–20",
-        "type": "number"
-      },
-      "q": {
-        "description": "Primary search query.",
-        "type": "string"
-      },
-      "query": {
-        "description": "Alias for q.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "query"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "required": [
+      "q"
+    ]
+  },
+  {
+    "required": [
+      "query"
+    ]
+  }
+]

addedInput schema / properties

Added value: +{
+  "limit": {
+    "default": 8,
+    "description": "Max results 1–20",
+    "type": "number"
+  },
+  "q": {
+    "description": "Primary search query.",
+    "type": "string"
+  },
+  "query": {
+    "description": "Alias for q.",
+    "type": "string"
+  }
+}

Changed4 schema fields changedSep 1, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "limit": {
+        "default": 8,
+        "description": "Max results 1–20",
+        "type": "number"
+      },
+      "q": {
+        "description": "Primary search query.",
+        "type": "string"
+      },
+      "query": {
+        "description": "Alias for q.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "q"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "limit": {
+        "default": 8,
+        "description": "Max results 1–20",
+        "type": "number"
+      },
+      "q": {
+        "description": "Primary search query.",
+        "type": "string"
+      },
+      "query": {
+        "description": "Alias for q.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "query"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties

Removed value: -{
-  "limit": {
-    "default": 8,
-    "description": "Max results 1–20",
-    "type": "number"
-  },
-  "q": {
-    "description": "Search query (alias: query)",
-    "type": "string"
-  }
-}

removedInput schema / required
```
Removed value: -[
-  "q"
-]
```

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A matching public notable-person profile.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Number of matches returned.",
+      "type": "number"
+    }
+  },
+  "required": [
+    "results",
+    "total"
+  ],
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so safety is covered. The description adds two things annotations don't: the catalog is public, and the call costs $0.01 — meaningful cost context for an agent deciding whether to invoke. It omits result-count/pagination behavior.

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?

Three short sentences, each carrying distinct information (what, when, example, cost), with the purpose front-loaded and nothing redundant.

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, return values need no explanation, and annotations cover the safety profile. The description is nearly complete; only minor gaps remain around result limits/pagination behavior and the q-vs-query alias beyond what the schema states.

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% (baseline 3), and the description adds a concrete slug example ('albert-einstein') that clarifies expected input format. It also names occupation as a searchable field, which the schema's generic 'q' does not convey.

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 specific verb and resource ('Search the public Dayze notable-people catalog') and enumerates the searchable dimensions (name, occupation, slug). This clearly separates it from the generic 'search' and from 'notable_profile'/'notable_pack' siblings.

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 the agent: 'Use when you need to find a person before fetching a pack,' which ties it to the notable_pack workflow. It gives no negative guidance (e.g., when to skip it or use a different lookup), so it falls short of 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.