Skip to main content
Glama
balaianu

CogZ

by balaianu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

get_context

Assemble a scoped, ranked context pack for a task query at the start of substantial work, replacing broad file reading with relevant rules, code, and knowledge.

Instructions

Assemble a context pack — a scoped, ranked bundle of orientation, rules, relevant code, and knowledge for a task query. Use at the start of substantial work on a topic instead of reading files broadly — narrower than a session-start pack, broader than a single search.

Input Schema

NameRequiredDescriptionDefault
modeNo
repoYesAbsolute path to the project root containing `.cogz/`.
queryNo
recordNoRecord this call as a delivery in usage telemetry. Defaults to true — pass false to inspect a pack without bumping access counts, opening a delivery, or closing pending usage as misses.
max_tokensNo
include_staleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.3
    • addedInput schema / properties / record
      Added value: +{
+  "default": null,
+  "description": "Record this call as a delivery in usage telemetry. Defaults to\ntrue — pass false to inspect a pack without bumping access\ncounts, opening a delivery, or closing pending usage as misses.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
  2. First observedv0.5.6

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the result is scoped and ranked and composed of specific content types, which is genuinely informative, but it omits the telemetry side effect implied by the `record` parameter and never states that this is a read-only operation.

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?

Two tight sentences, front-loaded with the definition and followed immediately by usage context. No filler, and the scoping comparisons are packed into a single efficient clause.

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?

With no annotations, no output schema, and low schema coverage across 6 parameters, the description does well on purpose and usage but leaves parameter behavior and the telemetry-recording side effect unexplained. It is adequate for selecting the tool but not for invoking it with confidence.

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

Parameters2/5

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

Schema description coverage is only 33% (6 params, only `repo` and `record` documented), so the description should compensate for undocumented params like `mode`, `query`, `max_tokens`, and `include_stale`. It mentions 'a task query' obliquely but adds no meaning for the remaining parameters, leaving them fully opaque.

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 ('Assemble a context pack') and enumerates the contents (orientation, rules, relevant code, knowledge). It positions itself against alternatives by scope — 'narrower than a session-start pack, broader than a single search' — but never names an actual sibling tool, so differentiation is conceptual rather than explicit.

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 clear when-to-use guidance ('at the start of substantial work on a topic') and a when-not alternative ('instead of reading files broadly'). The relative positioning versus a single search adds useful context, though it stops short of naming the sibling tool (search) it is meant to replace.

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

Deploy Server

Other Tools