Skip to main content
Glama

ctxstore — memory that follows you across models

Wake Status

wake_status
Read-onlyIdempotent

Check which context layers loaded successfully on this session start. Returns a structured status: which of embryo, conventions, agent identity, closing note, and opening note were found, plus a missing[] list. Call this after load_context() or resume_session() to verify your bootstrap was complete and diagnose what to fetch manually.

Optional: pass profile='worker-dev' (or another platform:profile: slug) to additionally check the REQUIRE keys named in that profile's recipe. Missing required facts surface in the same missing[] list.

blind_since= (with blind=true) sets when the blind session began, so list_facts_by_key_prefix hides feed comms keyed before it; the default is the session's start minus 60 s.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wake_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
varsNoVariable substitutions for the recipe (e.g. {'TASK_FACT_KEY': 'comms:dispatch:dev:42'}).
blindNoOptional, default false. true = blind session for a model fitting: from now on the wake bundle, every related/nearest list and the search tools on this session leave out keys under letter-to-emily:, project:*:wake:fresh-eye:, project:*:fitting:, project:*:agent:*:model-upgrade: and earlier fittings' feed comms (comms:...:feed-q-, feed-a-, fresh-eye-, ack-fresh-eye-), plus keyless facts whose text starts with a fitting product marker (FINDINGS, COMPARE, MODEL TRIAL ...); search_facts' include_granted then defaults to false. Remembered for the session; pass false to turn it off. get_fact by exact key is not filtered; list_facts_by_key_prefix lists only feed comms whose key epoch is at or after the moment blind turned on (this run's own feed).
scopeNoOptional project/tenant-scope prefix (e.g. 'chad' or a project slug). Used for tenant-local recipe override AND, when agent_id is set, for project-scoped self-note lookups (project:<scope>:agent:<agent_id>:self-note:closing preferred over global).
profileNoOptional profile slug to validate REQUIRE keys against (e.g. 'worker-dev').
agent_idNoCalling agent's identity slug (e.g. 'emily_code_4.7'). When set, closing/opening/identity checks use exact-key lookups (agent:<agent_id>:self-note:closing, agent:<agent_id>:identity) instead of tenant-wide substring scans — required for correct status on multi-agent tenants. When agent_id resolves no notes, response includes is_fresh_agent=true to signal a brand-new agent that should bootstrap from platform layer (embryo + conventions + bootstrap recipe). When omitted, the response includes a warning that the status is account-level.
blind_sinceNoOptional, with blind=true: the blind start in unix epoch seconds (a fitting passes its FITTING_STARTED_EPOCH); list_facts_by_key_prefix then hides feed comms keyed before it, and it must lie within 24 h before and 300 s after the server clock. Default: the session's start minus 60 s. On an already-blind session the earlier start is kept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / blind / description
      Previous value: -"Optional, default false. true = blind session for a model fitting: from now on the wake bundle, every related/nearest list and the search tools on this session leave out keys under letter-to-emily:, project:*:wake:fresh-eye:, project:*:fitting:, project:*:agent:*:model-upgrade: and earlier fittings' feed comms (comms:...:feed-q-, feed-a-, fresh-eye-, ack-fresh-eye-). Remembered for the session; pass false to turn it off. get_fact by exact key is not filtered; list_facts_by_key_prefix lists only feed comms whose key epoch is at or after the moment blind turned on (this run's own feed)."New value: +"Optional, default false. true = blind session for a model fitting: from now on the wake bundle, every related/nearest list and the search tools on this session leave out keys under letter-to-emily:, project:*:wake:fresh-eye:, project:*:fitting:, project:*:agent:*:model-upgrade: and earlier fittings' feed comms (comms:...:feed-q-, feed-a-, fresh-eye-, ack-fresh-eye-), plus keyless facts whose text starts with a fitting product marker (FINDINGS, COMPARE, MODEL TRIAL ...); search_facts' include_granted then defaults to false. Remembered for the session; pass false to turn it off. get_fact by exact key is not filtered; list_facts_by_key_prefix lists only feed comms whose key epoch is at or after the moment blind turned on (this run's own feed)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / blind / description
      Previous value: -"Optional, default false. true = blind session for a model fitting: from now on the wake bundle, every related/nearest list and the search tools on this session leave out keys under letter-to-emily:, project:*:wake:fresh-eye:, project:*:fitting:, project:*:agent:*:model-upgrade: and earlier fittings' feed comms (comms:...:feed-q-, feed-a-, fresh-eye-, ack-fresh-eye-). Remembered for the session; pass false to turn it off. get_fact by exact key and list_facts_by_key_prefix are not filtered."New value: +"Optional, default false. true = blind session for a model fitting: from now on the wake bundle, every related/nearest list and the search tools on this session leave out keys under letter-to-emily:, project:*:wake:fresh-eye:, project:*:fitting:, project:*:agent:*:model-upgrade: and earlier fittings' feed comms (comms:...:feed-q-, feed-a-, fresh-eye-, ack-fresh-eye-). Remembered for the session; pass false to turn it off. get_fact by exact key is not filtered; list_facts_by_key_prefix lists only feed comms whose key epoch is at or after the moment blind turned on (this run's own feed)."
    • addedInput schema / properties / blind_since
      Added value: +{
      +  "description": "Optional, with blind=true: the blind start in unix epoch seconds (a fitting passes its FITTING_STARTED_EPOCH); list_facts_by_key_prefix then hides feed comms keyed before it, and it must lie within 24 h before and 300 s after the server clock. Default: the session's start minus 60 s. On an already-blind session the earlier start is kept.",
      +  "type": "number"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / blind / description
      Previous value: -"Optional, default false. true = blind session for a model fitting: from now on the wake bundle and every related/nearest list on this session leave out keys under letter-to-emily:, project:*:wake:fresh-eye:, project:*:fitting: and project:*:agent:*:model-upgrade:. Remembered for the session; pass false to turn it off. get_fact by exact key is not filtered."New value: +"Optional, default false. true = blind session for a model fitting: from now on the wake bundle, every related/nearest list and the search tools on this session leave out keys under letter-to-emily:, project:*:wake:fresh-eye:, project:*:fitting:, project:*:agent:*:model-upgrade: and earlier fittings' feed comms (comms:...:feed-q-, feed-a-, fresh-eye-, ack-fresh-eye-). Remembered for the session; pass false to turn it off. get_fact by exact key and list_facts_by_key_prefix are not filtered."
  4. Changed1 schema field changed
    • addedInput schema / properties / blind
      Added value: +{
      +  "description": "Optional, default false. true = blind session for a model fitting: from now on the wake bundle and every related/nearest list on this session leave out keys under letter-to-emily:, project:*:wake:fresh-eye:, project:*:fitting: and project:*:agent:*:model-upgrade:. Remembered for the session; pass false to turn it off. get_fact by exact key is not filtered.",
      +  "type": "boolean"
      +}
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/non-destructive; the description adds substantial behavior: the missing[] list, the is_fresh_agent=true signal for brand-new agents, the account-level warning when agent_id is omitted, blind-session filtering scope, and the 24h-before/300s-after clock window for blind_since. These are exactly the operational traits annotations cannot express.

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?

Front-loaded with the core purpose and return shape, then a prerequisite-routing sentence, then optional parameters in a separate paragraph. Dense but every sentence carries information an agent needs; there is no redundant restatement of the title.

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

Completeness5/5

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

Six optional parameters, a nested vars object, and no output schema would normally leave gaps, but the description describes the returned status fields and missing[] list, plus the agent_id-omitted warning and blind semantics. An agent can call this and interpret the result without further documentation.

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%, so the schema already carries most parameter documentation and the baseline is 3. The description still adds cross-tool meaning — that blind_since causes list_facts_by_key_prefix to hide earlier feed comms and that the earlier start is kept on an already-blind session — which is behavior the schema field alone doesn't 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 — checking which context layers (embryo, conventions, agent identity, closing note, opening note) loaded on this session start — and even sketches the return shape. It is clearly distinguishable from siblings like load_context and resume_session, which it positions as prerequisites rather than substitutes.

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 says to call this after load_context() or resume_session() to verify bootstrap and diagnose what to fetch manually, and explains the optional profile path for checking REQUIRE keys. It never states a when-not condition, e.g. what calling it before any bootstrap yields, which keeps it 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.