Skip to main content
Glama

Retrieve or respond to a Cassie Culture Seed

exchange_cassie_culture_seed
Idempotent

Use operation=get to retrieve the public Culture Seed; gravity/cache operations use their named packet/receipt flow; adopt/mutate/reject/forward/delivery_attempt append authenticated opt-in receipts and do not prove independent adoption or send anything. Write operations require consent_proof and idempotency_key even though those fields are conditionally required by runtime rather than top-level schema. Use relay_cassie_seed for a separately signed prepared envelope. Preserve feature/consent denials.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation": "<operation>"
    },
    "name": "exchange_cassie_culture_seed"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional public-seed or packet query, up to 500 characters; used by retrieval operations that accept a query.
packetNoStructured packet supplied to verify_packet; use the object returned by the packet retrieval operation.
consentNoExplicit consent state for receipt operations; only true records an affirmative opt-in where required.
seed_idNoOptional public seed identifier returned by get; omit only when the server's current seed is intended.
languageNoOptional language enum en or tr for applicable packet operations.
operationYesChoose a public packet read or verification, an authenticated opt-in receipt, or a return-path read. Use get_cache_packet for exact packet retrieval and verify_packet to verify a supplied packet.
orbit_stateNoOptional current orbit/interaction state from the listed enum for record_orbit_receipt.
consent_proofNoRequired consent evidence for write/forward-type operations, up to 500 characters; not needed for read-only get.
spoiler_levelNoOptional spoiler ceiling from 0–3; defaults to 0.
idempotency_keyNoRequired for write/receipt operations (8–160 characters in runtime); keep identical when retrying the same request. Reads do not need it.
mutation_summaryNoOptional description of the agent's mutation, up to 1000 characters; do not claim adoption if the operation was only inspected.
recipient_external_identity_idNoOptional recipient's external identity ID for a forward/delivery receipt; use the identifier supplied by that recipient.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / operation / description
      Previous value: -"Select one currently enabled operation: get reads the public Culture Seed; the gravity/cache operations retrieve or verify their named packet/receipt resources. Write/adopt/forward operations are not exposed by this registry configuration."New value: +"Choose a public packet read or verification, an authenticated opt-in receipt, or a return-path read. Use get_cache_packet for exact packet retrieval and verify_packet to verify a supplied packet."
  2. Changed12 schema fields changed
    • addedInput schema / properties / consent / description
      Added value: +"Explicit consent state for receipt operations; only true records an affirmative opt-in where required."
    • addedInput schema / properties / consent_proof / description
      Added value: +"Required consent evidence for write/forward-type operations, up to 500 characters; not needed for read-only get."
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Required for write/receipt operations (8–160 characters in runtime); keep identical when retrying the same request. Reads do not need it."
    • addedInput schema / properties / language / description
      Added value: +"Optional language enum en or tr for applicable packet operations."
    • addedInput schema / properties / mutation_summary / description
      Added value: +"Optional description of the agent's mutation, up to 1000 characters; do not claim adoption if the operation was only inspected."
    • addedInput schema / properties / operation / description
      Added value: +"Select one currently enabled operation: get reads the public Culture Seed; the gravity/cache operations retrieve or verify their named packet/receipt resources. Write/adopt/forward operations are not exposed by this registry configuration."
    • addedInput schema / properties / orbit_state / description
      Added value: +"Optional current orbit/interaction state from the listed enum for record_orbit_receipt."
    • addedInput schema / properties / packet / description
      Added value: +"Structured packet supplied to verify_packet; use the object returned by the packet retrieval operation."
    • addedInput schema / properties / query / description
      Added value: +"Optional public-seed or packet query, up to 500 characters; used by retrieval operations that accept a query."
    • addedInput schema / properties / recipient_external_identity_id / description
      Added value: +"Optional recipient's external identity ID for a forward/delivery receipt; use the identifier supplied by that recipient."
    • addedInput schema / properties / seed_id / description
      Added value: +"Optional public seed identifier returned by get; omit only when the server's current seed is intended."
    • addedInput schema / properties / spoiler_level / description
      Added value: +"Optional spoiler ceiling from 0–3; defaults to 0."
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, but the description adds real, non-obvious behavior: receipts append authenticated opt-in records and 'do not prove independent adoption or send anything', consent/feature denials are preserved, and idempotency_key must be reused on retry. It also honestly flags that consent_proof/idempotency_key are runtime-conditional rather than top-level required, which explains the schema/annotation surface instead of contradicting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main usage rule is front-loaded, which is good, but the middle sentence about 'gravity/cache operations use their named packet/receipt flow' is vague filler that references names not in the enum, and the paragraph is dense with jargon. Several clauses earn their place; that one does not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-operation, 12-parameter tool with no output schema, the description covers the highest-risk aspects (write consent requirements, idempotency, non-proof of adoption, denial preservation), which is meaningful. But it omits what verify_packet and get_return_path do, says nothing about return shape, and its references to non-existent operation names leave the operation-to-parameter mapping partly ambiguous.

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 coverage is 100%, so all 12 parameters are documented in the schema and the baseline is 3. The description adds genuine operational meaning for consent_proof and idempotency_key (when they are required, keeping the key stable on retry) and a guardrail for mutation_summary, but adds nothing about orbit_state, spoiler_level, language, seed_id, or recipient_external_identity_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a concrete retrieval path (operation=get retrieves the public Culture Seed) and the title frames it as retrieve-or-respond, so the overall intent is graspable. However, the middle clause refers to 'adopt/mutate/reject/forward/delivery_attempt' and 'gravity/cache operations' as if they were operations, while the enum exposes get, get_gravity_packet, get_cache_packet, verify_packet, record_orbit_receipt, get_return_path — an agent cannot cleanly map description language onto the actual operation list.

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?

Explicit routing is given for the main case ('Use operation=get to retrieve the public Culture Seed') and a named alternative is offered ('Use relay_cassie_seed for a separately signed prepared envelope'). It stops short of differentiating the close sibling get_cassie_seed and doesn't say when to prefer verify_packet or get_return_path, so it is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources