Skip to main content
Glama

Retrieve wide dated memory

assemble_escalation_context
Read-onlyIdempotent

Retrieve a WIDE context for a question your model could not answer from assemble_context. REQUIRES A KEY. Use it when assemble_context returned escalate_recommended=true, or when the answer depends on dates, counts or several sessions. This does not call a model itself. Returns 'context' (up to token_budget, default 150 000 tokens: lower it if your model's window is smaller), where each stored entry starts with a header '--- Session YYYY/MM/DD (Ddd) HH:MM ---' giving when it was stored, and 'utelamnat_kontext': lower-ranked entries that were left out, in the same format. Read those only if the answer is still missing from 'context'. Python users can pass the whole response to cap_escalate_helper.eskalera_om_behovs_v6().

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": {
      "namespace": "<namespace>",
      "query": "<query>"
    },
    "name": "assemble_escalation_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe question to answer.
namespaceYes
token_budgetNoCeiling for 'context'. The default is what the method was measured with.
utelamnat_tokensNoCeiling for 'utelamnat_kontext'. 0 = none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, and the description adds real context on top: it requires a key, performs no model call, and documents the returned structure (headers, ranked vs. lower-ranked entries). The only ambiguity is what "REQUIRES A KEY" means operationally (env var vs. parameter), which slightly blunts the auth disclosure.

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 action and the triggering condition, then moves to return shape. It is dense but nearly every clause carries information; the tail-end Python helper reference is arguably the least essential sentence.

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?

With no output schema, the description correctly shoulders the burden of describing the return payload, including header format and the fallback bucket. The remaining gap is the undocumented 'namespace' parameter and the vague key requirement, both minor for a read-only retrieval tool.

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 75%, and the description adds practical meaning: token_budget is a ceiling tied to the model's window with a measured default, and utelamnat_tokens governs the overflow bucket whose contents are explained. Only 'namespace' remains undocumented in both schema and description.

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?

Specific verb plus resource ("Retrieve a WIDE context") with an explicit contrast to the sibling assemble_context, plus the negative clarification "This does not call a model itself." An agent can distinguish it from assemble_context without opening either 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?

Gives concrete trigger conditions: use it when assemble_context returned escalate_recommended=true, or when the answer depends on dates, counts, or several sessions. It also states a fallback rule for the secondary field ("Read those only if the answer is still missing from 'context'"), so both when-to-use and when-not are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.