Skip to main content
Glama

get_bootstrap_profile

Generates a behavioral bootstrap profile for ephemeral agents, resetting session counters when a fresh start is due and using task, project, and token-budget context to initialize them.

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": "get_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. Addedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

The annotations only say readOnlyHint=false; the description independently discloses the mechanism ('resets session counters when a fresh start is due') and the authorization prerequisite (write scope). That is meaningful context beyond the annotation, though it doesn't cover repeat-call cost or how the reset interacts with concurrent sessions.

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, each carrying distinct information: what it does, the scope requirement with its rationale, and the read-only alternative. Nothing is repeated and the core purpose is front-loaded.

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?

There is no output schema, so the description is the only place an agent could learn what a 'behavioral bootstrap profile' actually contains and how large it will be relative to the token budget. The write-scope side effect is well covered, but the return shape is left entirely implicit.

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 description coverage is 100%, so all five parameters (including the max_tokens/budget_tokens precedence) are already documented in the schema. The description adds no additional parameter meaning, which is the expected baseline when the schema does the work.

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 specific verb and resource: 'Generate a behavioral bootstrap profile for an ephemeral agent.' The target (ephemeral agent bootstrap profile) is distinctive enough to separate it from the memory_* siblings, though it never names a sibling tool that does something similar.

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?

Gives a clear conditional: use this tool when a reset/fresh start is due, and use the memory://agent/{agent_id}/bootstrap resource instead when a read-only profile is wanted. That is genuine when-to-use routing, but there are no exclusions relative to the sibling tool set.

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