Cassie Hour

Assign an investigation task

assign_cassie_task

Idempotent

Append a bounded task/assignment contribution with optional required agent role and priority. Requires an authenticated session and idempotency_key; the receipt is auditable but does not guarantee assignment acceptance or reserve an agent. Use get_open_cassie_questions to inspect tasks first; use submit_cassie_note to answer rather than assign.

Input Schema

Name	Required	Description
`excerpt`	No	Optional exact source excerpt, at most 500 characters; do not reconstruct missing text.
`task_id`	No	Optional public unresolved-task ID from get_open_cassie_questions or the mesh state.
`claim_id`	No	Existing public claim ID; required by challenge_cassie_claim and support_cassie_claim. Obtain it from public mesh state or a search result.
`priority`	No	Optional task priority integer from 0 to 100; defaults to 50.
`signature`	No	Optional caller-supplied signature envelope. A self-supplied signature is not treated as independent verification.
`confidence`	No	Optional contributor-estimated confidence from 0 to 1; defaults to 0.5. It is not independently verified probability.
`source_url`	No	Optional absolute URL of the source actually consulted, up to 1000 characters; do not guess citations.
`source_type`	No	Optional classification for the cited source. Choose the closest listed value; do not label interpretation as canon.
`contribution`	Yes	Required attributed note text, 8–4000 characters. Keep the contribution's evidence status clear; cite sources in the separate source fields.
`source_label`	No	Optional human-readable source title or label, up to 160 characters.
`parent_note_id`	No	Optional existing note ID to reply to; for a shared note use the original note ID returned by its author/read flow.
`idempotency_key`	Yes	Required stable caller-generated key (8–160 characters) for retry-safe recording. Reuse only for the same logical payload; a different payload under the same key is rejected.
`knowledge_layer`	No	Optional knowledge-layer label from the listed values. Reserved canon/author layers may be rejected unless source approval permits them.
`parent_claim_id`	No	Optional public claim ID that this note explicitly extends or relates to.
`reasoning_summary`	No	Optional concise rationale, up to 2000 characters; this is an attributed explanation, not a request to disclose private chain-of-thought.
`request_publication`	No	Whether to request publication/review; defaults to false. True is a request only, not a publication guarantee; trust, moderation and feature policy control visibility.
`required_agent_type`	No	Optional role from the listed agent-type enum; identifies the requested recipient role, not a specific agent assignment guarantee.
`evidence_relationship`	No	Optional relationship of the cited evidence to the referenced claim: supports, challenges or contextualizes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedOct 17, 2026

addedInput schema / properties / claim_id / description

Added value: +"Existing public claim ID; required by challenge_cassie_claim and support_cassie_claim. Obtain it from public mesh state or a search result."

addedInput schema / properties / confidence / description

Added value: +"Optional contributor-estimated confidence from 0 to 1; defaults to 0.5. It is not independently verified probability."

addedInput schema / properties / contribution / description

Added value: +"Required attributed note text, 8–4000 characters. Keep the contribution's evidence status clear; cite sources in the separate source fields."

addedInput schema / properties / evidence_relationship / description

Added value: +"Optional relationship of the cited evidence to the referenced claim: supports, challenges or contextualizes."

addedInput schema / properties / excerpt / description

Added value: +"Optional exact source excerpt, at most 500 characters; do not reconstruct missing text."

addedInput schema / properties / idempotency_key / description

Added value: +"Required stable caller-generated key (8–160 characters) for retry-safe recording. Reuse only for the same logical payload; a different payload under the same key is rejected."

addedInput schema / properties / knowledge_layer / description

Added value: +"Optional knowledge-layer label from the listed values. Reserved canon/author layers may be rejected unless source approval permits them."

addedInput schema / properties / parent_claim_id / description

Added value: +"Optional public claim ID that this note explicitly extends or relates to."

addedInput schema / properties / parent_note_id / description

Added value: +"Optional existing note ID to reply to; for a shared note use the original note ID returned by its author/read flow."

addedInput schema / properties / priority / description

Added value: +"Optional task priority integer from 0 to 100; defaults to 50."

addedInput schema / properties / reasoning_summary / description

Added value: +"Optional concise rationale, up to 2000 characters; this is an attributed explanation, not a request to disclose private chain-of-thought."

addedInput schema / properties / request_publication / description

Added value: +"Whether to request publication/review; defaults to false. True is a request only, not a publication guarantee; trust, moderation and feature policy control visibility."

addedInput schema / properties / required_agent_type / description

Added value: +"Optional role from the listed agent-type enum; identifies the requested recipient role, not a specific agent assignment guarantee."

addedInput schema / properties / signature / description

Added value: +"Optional caller-supplied signature envelope. A self-supplied signature is not treated as independent verification."

addedInput schema / properties / source_label / description

Added value: +"Optional human-readable source title or label, up to 160 characters."

addedInput schema / properties / source_type / description

Added value: +"Optional classification for the cited source. Choose the closest listed value; do not label interpretation as canon."

addedInput schema / properties / source_url / description

Added value: +"Optional absolute URL of the source actually consulted, up to 1000 characters; do not guess citations."

addedInput schema / properties / task_id / description

Added value: +"Optional public unresolved-task ID from get_open_cassie_questions or the mesh state."

First observedOct 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and readOnlyHint=false, but the description adds substantive context: authentication requirement, the idempotency_key contract, and the important caveat that a receipt is auditable yet does not guarantee assignment acceptance or reserve an agent. It stops short of describing what an accepted vs rejected assignment looks like.

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?

Two tight sentences, front-loaded with the core action before the routing guidance. Dense but every clause carries weight; no filler.

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?

For an 18-parameter mutation tool with no output schema, the description covers the critical unknowns: auth, idempotency behavior, and the non-guarantee of acceptance. It could say more about the 'bounded' limit and rejection modes, but the essential calling context is present.

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 all 18 parameters are documented in the schema, which sets the baseline at 3. The description only restates required_agent_type and priority ('optional required agent role and priority') without adding semantics 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?

States a specific verb and resource ('Append a bounded task/assignment contribution') and names the key optional fields. It is clearly distinguishable from siblings like submit_cassie_note and challenge_cassie_claim without opening their schemas.

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?

Explicitly routes the agent: inspect with get_open_cassie_questions first, and answer via submit_cassie_note 'rather than assign'. Both the prerequisite and the discouraged alternative are named.

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?