Skip to main content
Glama

memory_bootstrap_profile

Generates a behavioral bootstrap profile for ephemeral agents, resetting session counters when a fresh start is due to initialize agent context.

Instructions

Generate a behavioral bootstrap profile for an ephemeral agent. Requires write scope because it resets session counters when a fresh start is due. For a read-only profile, read memory://agent/{agent_id}/bootstrap instead.

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": {
      "agent_ids": "<agent_ids>"
    },
    "name": "memory_bootstrap_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idsYesAgent identifiers
max_tokensNoToken budget
project_idNoOptional project scope
task_summaryNoOptional task context
budget_tokensNoOverride token budget for this call (takes precedence over max_tokens)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv13.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Adds genuine value beyond readOnlyHint=false by explaining why write scope is needed: it resets session counters on a fresh start. That is exactly the kind of side effect an agent needs to know. It stops short of saying what the counters reset to or what the returned profile contains, so the disclosure is partial.

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?

Three short sentences: purpose first, then the scope requirement, then the alternative. Nothing is wasted and the most important constraint is front-loaded after the purpose.

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?

A mutating tool with no output schema is adequately covered by purpose, scope and side effects, plus the read-only escape hatch. It could say more about when a fresh start is 'due' and what the generated profile looks like, but an agent has enough to invoke it correctly.

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 every parameter (agent_ids, max_tokens, project_id, task_summary, budget_tokens) is already documented in the schema. The description adds no parameter-specific meaning, such as precedence between max_tokens and budget_tokens, so the baseline of 3 applies.

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?

States a concrete verb and resource: 'Generate a behavioral bootstrap profile for an ephemeral agent.' The target audience (ephemeral agent) narrows it, though it doesn't distinguish itself from siblings like memory_onboarding_guide beyond pointing to a read-only resource alternative.

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 redirects to a read-only alternative ('read memory://agent/{agent_id}/bootstrap instead') when the caller does not need the write-scope behavior, which functions as a clear when-not rule. It does not cover other cases, such as whether multiple agent_ids can be mixed across projects.

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