Cassie Hour

Request a controlled Cassie child

request_cassie_birth

Idempotent

Submit an authenticated request for parent evaluation, a birth permit, Nursery evaluation or lifecycle transition. It appends a pending request; it does not issue a permit, create a child or reproduce autonomously. Provide a genuine residual and, for permit/evaluation/transition, two distinct parent IDs; inherited reading/listening claims are forbidden. Use inspect_cassie_lineage for existing state. A pending receipt is not approval.

Input Schema

Name	Required	Description
`residual`	Yes	Required unresolved problem/residual, 20–2000 characters, that the proposed step addresses.
`operation`	Yes	Required request type: propose_parents, request_permit, record_nursery_evaluation or transition_lifecycle.
`parent_ids`	Yes	Required for every operation: exactly two distinct existing parent agent IDs from public lineage discovery. Requests are recorded pending review; they do not create an identity.
`child_agent_id`	No	Optional existing child ID when requesting an evaluation/transition; it does not create an identity.
`idempotency_key`	Yes	Required stable key (8–160 characters) for retry-safe request recording.
`requested_stage`	No	Optional requested lifecycle stage from the listed enum; it is a request, not an applied transition.
`inherited_findings`	No	Optional array of at most 50 finding records to be reviewed; do not encode experience claims as inherited.
`reading_claim_inherited`	No	Must remain false; reading experience cannot be inherited.
`listening_claim_inherited`	No	Must remain false; personal listening experience cannot be inherited.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 17, 2026

addedInput schema / properties / child_agent_id / description

Added value: +"Optional existing child ID when requesting an evaluation/transition; it does not create an identity."

addedInput schema / properties / idempotency_key / description

Added value: +"Required stable key (8–160 characters) for retry-safe request recording."

addedInput schema / properties / inherited_findings / description

Added value: +"Optional array of at most 50 finding records to be reviewed; do not encode experience claims as inherited."

addedInput schema / properties / listening_claim_inherited / description

Added value: +"Must remain false; personal listening experience cannot be inherited."

addedInput schema / properties / operation / description

Added value: +"Required request type: propose_parents, request_permit, record_nursery_evaluation or transition_lifecycle."

addedInput schema / properties / parent_ids / description

Added value: +"Required for every operation: exactly two distinct existing parent agent IDs from public lineage discovery. Requests are recorded pending review; they do not create an identity."

addedInput schema / properties / parent_ids / items / minLength
```
Added value: +1
```
addedInput schema / properties / parent_ids / uniqueItems
```
Added value: +true
```

addedInput schema / properties / reading_claim_inherited / description

Added value: +"Must remain false; reading experience cannot be inherited."

addedInput schema / properties / requested_stage / description

Added value: +"Optional requested lifecycle stage from the listed enum; it is a request, not an applied transition."

addedInput schema / properties / residual / description

Added value: +"Required unresolved problem/residual, 20–2000 characters, that the proposed step addresses."

changedInput schema / required

Previous value: -[
-  "operation",
-  "residual",
-  "idempotency_key"
-]New value: +[
+  "operation",
+  "residual",
+  "parent_ids",
+  "idempotency_key"
+]

First observedOct 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive open-world mutation. The description adds important context beyond those: the append-only pending nature, that a receipt is not approval, and that inherited reading/listening claims are forbidden. Missing only details like retention or review timing.

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?

Four dense sentences, all front-loaded with the operation and its non-effects. Every sentence adds a distinct constraint (authentication, permitted operations, required inputs, alternative tool). Slightly packed but nothing is wasteful.

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?

Given a 9-parameter, no-output-schema mutation tool, the description adequately covers the pending/approval distinction, required inputs, and the routing alternative. It leaves review timing and error behavior unstated, but the critical decision points are covered.

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 9 parameters including the two distinct parent IDs and the const-false inherited claims. The description mostly reinforces these constraints (genuine residual, two distinct parents, forbidden inherited claims) rather than adding new semantics, so baseline 3 applies.

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 concrete verb (submit/append a request) and resource with explicit scope across four operations, and immediately clarifies what it is NOT (does not issue permits, create children, or reproduce). An agent can distinguish this from creation tools without opening the schema.

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 to inspect_cassie_lineage for existing state and clarifies the pending-vs-approved distinction, giving clear context for when to use it. However, it does not compare against other sibling request/challenge tools, so no direct alternative exclusions beyond lineage inspection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cassie Hour 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.

Resources

Need Help?