Skip to main content
Glama

krusch_context_retrieve

Read-onlyIdempotent

Retrieves active project memories, steering rules, and state briefings within a token budget, enabling AI coding agents to load relevant context for a query.

Instructions

Universal context retrieval tool. Pulls active project memories, steering rules, and state briefings respecting token budget limits.

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

Input Schema

NameRequiredDescriptionDefault
modeNoRetrieval modehybrid
queryYesSearch query or topic
projectNoTarget project (auto-detected if omitted)
categoryNoOptional closed category filter
limit_tokensNoMaximum token budget to return
include_stateNoOptionally prepend compiled state briefing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that output is bounded by a token budget and enumerates the content types retrieved, but it doesn't say what happens when the budget is exceeded (truncation, ordering, priority) or how results are ranked.

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?

Two short sentences, front-loaded with the core purpose, with no filler. 'Universal' is the only slightly vague word, but it costs little space.

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 six fully documented parameters, annotated safety hints, and no output schema, the description covers the essentials for a read-only retrieval tool. The missing piece is return-shape and budget-exhaustion behavior, which is a moderate rather than critical gap for a read operation.

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%, with enums and defaults documented inline, so the baseline is 3. The description mentions token budget limits, loosely echoing limit_tokens, but adds no syntax, interaction, or precedence details beyond the schema.

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?

The description names a specific verb (pulls) and concrete resources (project memories, steering rules, state briefings), plus a constraint (token budget). It is clear what the tool returns, but it doesn't distinguish itself from siblings like krusch_context_nudge or krusch_context_health beyond the word 'retrieval.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Calling itself 'universal' implies this is the default retrieval entry point, but there is no explicit when-to-use or when-not-to-use guidance, and no named alternative for narrower lookups. Usage is only implied.

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