Dayze — Life Context

Berklee Relationship Map

get_berklee_relationship_map

Read-only

Read-only owner view of the 2012–2015 Berklee email archive: per-person first/last cited contact, imported message volume, explicitly stored courses/projects, and email-anchor versus name-only provenance. Optional exact course, term, and project filters. Every cited event carries an inspect_url. Volume is not closeness; silence is not interpreted. Identity-document, health, and legal records are excluded. ($0.15; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`term`	No	Exact term facet, e.g. Fall 2014.
`course`	No	Exact stored course facet.
`project`	No	Exact stored project facet.

Output Schema

TableJSON Schema

Name	Required	Description
`facets`	Yes	Available course, term, and project filter values.
`people`	Yes
`period`	Yes	Fixed college archive window, 2012-01-01 through 2015-12-31.
`account`	Yes	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`caveats`	Yes
`filters`	Yes	Exact course, term, and project filters applied.
`truncated`	Yes
`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.
`record_count`	Yes
`active_correction_count`	Yes
`correction_history_count`	Yes
`correction_history_available`	Yes
`excluded_sensitive_record_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 2026

addedOutput schema / properties / correction_history_available
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "account",
-  "period",
-  "filters",
-  "people",
-  "facets",
-  "record_count",
-  "excluded_sensitive_record_count",
-  "active_correction_count",
-  "correction_history_count",
-  "truncated",
-  "caveats"
-]New value: +[
+  "account",
+  "period",
+  "filters",
+  "people",
+  "facets",
+  "record_count",
+  "excluded_sensitive_record_count",
+  "correction_history_available",
+  "active_correction_count",
+  "correction_history_count",
+  "truncated",
+  "caveats"
+]

Changed3 schema fields changedOct 3, 2026

addedOutput schema / properties / active_correction_count
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / correction_history_count
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / required

Previous value: -[
-  "account",
-  "period",
-  "filters",
-  "people",
-  "facets",
-  "record_count",
-  "excluded_sensitive_record_count",
-  "truncated",
-  "caveats"
-]New value: +[
+  "account",
+  "period",
+  "filters",
+  "people",
+  "facets",
+  "record_count",
+  "excluded_sensitive_record_count",
+  "active_correction_count",
+  "correction_history_count",
+  "truncated",
+  "caveats"
+]

AddedOct 3, 2026

TDQS

A3.7/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint/destructiveHint annotations: it discloses cost ($0.15), an API key requirement, explicit data exclusions (identity-document, health, legal records), and interpretation caveats ('volume is not closeness; silence is not interpreted') plus per-event inspect_url provenance. This is exactly the extra context annotations cannot carry.

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?

A single dense but front-loaded paragraph; the core purpose leads, then filters, provenance, caveats, exclusions, and pricing. Every sentence carries information, though the packing makes it slightly heavy to scan.

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 not be explained, and the description still covers filters, provenance model, exclusions, cost, and auth. Complete enough to call correctly; only sibling differentiation 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?

Schema description coverage is 100% and each param is already documented as an 'exact ... facet', so the description adds little beyond confirming they are optional filters. 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 resource and scope: a read-only owner view of the 2012–2015 Berklee email archive, enumerating the exact facets returned (first/last cited contact, message volume, stored courses/projects, provenance). The purpose is unmistakable, but it never names or distinguishes itself from siblings like get_person_connections or get_person_neighborhood, so an agent cannot route between them from the text alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It notes that course/term/project filters are optional but gives no when-to-use guidance, no prerequisites, and no comparison to alternative relationship/person-graph tools. The agent must infer that this is a Berklee-archive-specific view rather than the general people graph.

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.