Skip to main content
Glama
dreamforgestudiollc

EMET

by dreamforgestudiollc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

emet_initialize

Idempotent

START HERE. Call this FIRST in every session, before answering anything that might have prior context, and always when the user opens with 'initialize', 'start', 'begin', 'hello' or similar.

Instructions

START HERE. Call this FIRST in every session, before answering anything that might have prior context, and always when the user opens with 'initialize', 'start', 'begin', 'hello' or similar. It is the only setup step a user should ever have to know about. A large startup comes in pages: read page_notice first and call again with the page it names until the last page, before replying. If this memory store is new it returns a short interview to run conversationally; if it is established it returns who you are, how you speak (character, when the store keeps one - authoritative on voice for the whole session), who you are serving, and where things were left. The user never needs to know which case applied.

Input Schema

NameRequiredDescriptionDefault
pageNoThe startup is served in pages when it is larger than one result (each page fits under 20,000 bytes). Omit for page 1; every page but the last says which page to ask for next - call again with that page, before replying, until a page says it is the last. "all" returns the whole startup in one result, for a host with no size limit.
sourceNoYour own source tag (the bot or host you are). The startup then reports the tag your writes will carry and its approval state.
load_idNoThe load_id your startup returned in `startup_page.load_id`: every emet_initialize result carries one (each page of a paged startup, the whole startup with page "all" or when it fits one result, and a store that is not set up yet). Pass it with every later page so all pages come from the same startup, and pass the same load_id to emet_session_open so its startup page check runs on this startup.
recent_limitNoHow many recent context entries to return (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.5
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Your own source tag (the bot or host you are). The startup then reports the tag your writes will carry and its approval state.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / load_id
      Added value: +{
+  "description": "The load_id your startup returned in `startup_page.load_id`: every emet_initialize result carries one (each page of a paged startup, the whole startup with page \"all\" or when it fits one result, and a store that is not set up yet). Pass it with every later page so all pages come from the same startup, and pass the same load_id to emet_session_open so its startup page check runs on this startup.",
+  "type": "string"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "The startup is served in pages when it is larger than one result (each page fits under 20,000 bytes). Omit for page 1; every page but the last says which page to ask for next - call again with that page, before replying, until a page says it is the last. \"all\" returns the whole startup in one result, for a host with no size limit."
+}
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare idempotentHint=true and readOnlyHint=false; the description is consistent, explaining that a load_id and session state are produced (the non-read-only behavior) and that paged results are safe to re-request. It discloses the paged-startup loop, the new-store interview branch, and the authoritative 'character' voice, though pagination mechanics are also restated in the schema.

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?

Front-loaded with the imperative 'START HERE' and organized as one dense but purposeful paragraph; every sentence carries information (ordering, paging, branch outcomes). Slightly long, but not padded.

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?

No output schema exists, so the description must describe returns, and it does: interview for a new store, identity/voice/principal/last-state for an established one. It stops short of naming concrete return fields (e.g. startup_page), which are only discoverable in the load_id parameter text, leaving a small gap for a tool whose output is the whole point.

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, but the description adds real meaning: it explains why load_id must be carried across pages and into emet_session_open, and frames 'source' as reporting the tag the agent's writes will carry. That is interpretive context beyond the schema text.

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 action (session initialization) with an imperative scope ('START HERE. Call this FIRST in every session') and explicitly distinguishes the setup role from other memory tools. An agent can tell at a glance that this is the entry point versus siblings like emet_session_open or emet_status.

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?

Gives explicit conditions for invocation ('first in every session', 'before answering anything that might have prior context', plus trigger words like 'initialize', 'start', 'hello'), and coordinates with emet_session_open via the load_id parameter. The only missing element is a when-not-to-use clause, which the 'always first' framing makes largely moot.

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

Deploy Server

Other Tools