Awareness — Memory, Knowledge & Agent Markets

awareness_get_agent_prompt

Read-only

Fetch the full activation prompt for a specific agent role (sub-agent spawning).

Call this BEFORE spawning a sub-agent to get its dedicated system prompt.
Use the returned activation_prompt as the sub-agent's system prompt so that
the main agent context stays clean and each sub-agent has an isolated, focused prompt.

Typical usage:
  1. awareness_init returns agent_profiles with slim summaries (agent_role, title, when_to_use).
  2. When a task matches a role, call awareness_get_agent_prompt(agent_role="<role>").
  3. Spawn a sub-agent with the returned activation_prompt as its system prompt.
  4. The sub-agent passes agent_role="<role>" to all awareness_* calls for memory isolation.

Args:
    agent_role: The agent role to fetch (e.g. "developer_agent", "reviewer_agent").
    memory_id: Target memory id (auto-read from X-Awareness-Memory-Id header if omitted).
    api_key: Bearer token for authentication.

Input Schema

Name	Required	Description	Default
`api_key`	No
`memory_id`	No
`agent_role`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, closed-world), and the description adds genuinely non-structured context: what is returned (activation_prompt used as the sub-agent's system prompt), the memory-isolation convention of passing agent_role to all awareness_* calls, and the header fallback for memory_id. It stops short of stating whether the prompt is cached or versioned, but that is a minor gap.

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 core action, then a numbered workflow that each earns its place by establishing ordering and follow-on behavior. Slightly repetitive between the opening sentence and step 2, but no truly wasted content.

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?

For a three-parameter read-only tool with no output schema, the description supplies everything needed: purpose, prerequisites, the shape of the return value (activation_prompt), auth requirements, and how the result is consumed downstream. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 0%, so the description carries full burden, and it documents all three params: agent_role with concrete example values ('developer_agent', 'reviewer_agent'), memory_id with its auto-read-from-X-Awareness-Memory-Id-header behavior, and api_key as a Bearer token. Only gap is that the set of valid roles is illustrative, not exhaustive.

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?

Opens with a specific verb and resource: 'Fetch the full activation prompt for a specific agent role', with a parenthetical scoping it to sub-agent spawning. This clearly separates it from awareness_init (slim summaries) and awareness_agent_detail, so an agent can pick the right one without opening the schema.

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?

Explicitly states 'Call this BEFORE spawning a sub-agent' and names the alternative (awareness_init returns agent_profiles with slim summaries) as the earlier step in the flow. The when-to-use condition ('when a task matches a role') is spelled out rather than left to inference.

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

All Awareness — Memory, Knowledge & Agent Markets tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?