Skip to main content
Glama
templetwo
by templetwo

prior_for_turn

Retrieve a compact priors block at the start of a turn, assembled from recent drift, unresolved uncertainty, matched threads, and related insights. A freshness penalty prevents repeated surfacing.

Instructions

Turn-start reflex. Call at the start of a turn (not session) to receive a compact priors block assembled from four sources in priority order: recent drift (Nape honk) → oldest unresolved uncertainty → top matched open thread → top related insight. Enforces k=1 per bucket by default (ReasoningBank ICLR 2026: k>1 hurts), a hard token cap, and a freshness penalty that demotes items surfaced in the last 3 calls — so the same memory cannot keep resurfacing and amplifying itself (Jain et al. MIT/IDSS 2026 sycophancy guardrail). Read the returned 'block' before forming the turn's response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domain_tagsNoActive domain tags for this turn. If empty, drift + uncertainty still surface but threads/insights are skipped.
projectNoOptional project for +0.5 match bonus.
kNoItems per bucket (capped at 3). Default 1 per ReasoningBank finding.
max_tokensNoHard ceiling on the returned block's token count.
dry_runNoIf true, does not write to the freshness log. Use for preview.
full_contentNoWhen true, removes the per-item 120-char cap inside the priors block so addressed-letter shapes survive. The token budget still applies — the block as a whole won't exceed max_tokens. Default false preserves compact pre-attentive surface.
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: priority order, k=1 enforcement, hard token cap, freshness penalty demoting recently surfaced items, and citations to academic papers. It comprehensively describes what the tool does and its safeguards.

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?

The description is information-dense and front-loaded with the key action. Every sentence adds value, though it is slightly lengthy. It could be trimmed without losing clarity, but it remains efficient.

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?

Given the tool's complexity (6 params, no output schema), the description covers parameters and behavior well. It explains the returned 'block' concept but does not detail its internal structure, which might be needed for full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning beyond the schema. It explains the priority order of sources, default k=1 reasoning, token cap behavior, and effects of flags like dry_run and full_content. This enriches parameter understanding.

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?

The description clearly states the tool's purpose: 'Turn-start reflex. Call at the start of a turn (not session) to receive a compact priors block assembled from four sources.' The verb 'receive' and resource 'priors block' are specific, and the description distinguishes it from siblings by its unique role as a turn-start reflex.

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?

The description provides explicit when-to-use guidance: 'Call at the start of a turn (not session).' It also advises to 'Read the returned block before forming the turn's response.' However, it lacks explicit alternatives or when-not-to-use scenarios, though the sibling list implies distinct tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/templetwo/sovereign-stack'

If you have feedback or need assistance with the MCP directory API, please join our Discord server