Skip to main content
Glama

emet_status

Idempotent

Run a one-call health diagnostic covering environment, database, vector index, document presence, and per-layer counts; optionally probe the write path or check session and checkpoint state.

Instructions

Diagnostic in one call (replaces emet_setup_status, get_status and emet_verify_connection, 2026-09-27). Reports environment, database, collections, vector index, whether identity and user documents exist, and per-layer counts and health. Pass probe: true to also prove the write path - connect, write a probe document, read the same value back, remove it; a read alone cannot reveal a broken write path. Pass session_id to read that session: session.state is open, closed, or absent, or unreadable when the session row cannot be read (the rest of the status still returns, and the asked id is not echoed). A part id is read as its base session. Prefer emet_initialize for a normal session start. Also reports checkpoint on every call: due when an open session's last verbatim save, or the open itself when no transcript is saved, is at least 24 hours old. A session covered by a current conforming records/ disposition (templates/SESSIONDISPOSITION.md) is not listed as checkpoint-due. A row that names an inserted_id dispositions that transcript only and does not close the session. The disposition is not a receipt. Save that verbatim text with emet_transcript_append or save_transcript, under the open session or the daily YYYY-MM-DD_chat-daily session. emet_session_close cites the saved parts. A store that cannot be read sets checkpoint.unread and does not claim the save is current.

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": "emet_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
probeNoAlso write and read back a probe document (default false). Use after a deploy or a configuration change.
sourceNoYour own source tag. The status then reports the tag your writes will carry and its approval state.
session_idNoA transcript session id from emet_session_open, or one of its part ids. The result's session.state is open, closed, or absent, or unreadable when that session cannot be read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.2
    • addedInput schema / properties / session_id
      Added value: +{
      +  "description": "A transcript session id from emet_session_open, or one of its part ids. The result's session.state is open, closed, or absent, or unreadable when that session cannot be read.",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.2.5
    • addedInput schema / properties / source
      Added value: +{
      +  "description": "Your own source tag. The status then reports the tag your writes will carry and its approval state.",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

It explains why readOnlyHint=false: probe actually connects, writes a probe document, reads it back and removes it, which the annotations cannot convey. It also discloses failure behavior (an unreadable session row still returns the rest of the status and does not echo the id; an unreadable store sets checkpoint.unread rather than claiming the save is current), which is exactly the beyond-annotation context this dimension rewards.

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?

Purpose is front-loaded, which is good, but the checkpoint/disposition block sprawls across many sentences with stacked subordinate clauses ('due when an open session's last verbatim save, or the open itself when no transcript is saved, is at least 24 hours old'), and the disposition rules read as workflow policy rather than tool definition.

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 no output schema, the description carries the burden of describing return content, and it does so at a useful level (per-layer counts and health, session.state enum values, checkpoint fields). It stops short of characterizing the shape of 'health' or what layers appear, but an agent can call it confidently.

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 baseline is 3; the description earns more by adding semantics not in the schema, notably that 'A part id is read as its base session' and that an unreadable session still yields the remaining status without echoing the requested id. It says nothing about the 'source' parameter beyond what the schema already declares.

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?

The description enumerates exactly what the call returns (environment, database, collections, vector index, identity/user documents, per-layer counts and health) and names the tools it replaces, so the resource is unambiguous. The opener 'Diagnostic in one call' is vaguer than the enumeration that follows, and several sentences drift into checkpoint/disposition semantics rather than core purpose.

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?

It gives a clear conditional for the expensive mode ('Pass probe: true ... Use after a deploy or a configuration change' via the schema guidance, and 'a read alone cannot reveal a broken write path') and explicitly routes normal session starts elsewhere: 'Prefer emet_initialize for a normal session start.' It does not state when a plain status call is worth making versus e.g. query_layer or emet_setup_complete.

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