Skip to main content
Glama
AlaeddineMessadi

ContextPro

by AlaeddineMessadi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

task_pack

Read-onlyIdempotent

Assemble a minimal working set for a coding task: ranked files, nearby tests, recent diffs, project memory, and risks, so agents start with the context they need.

Instructions

Assemble the minimum useful working set for a task: ranked files, nearby tests, recent diffs, memory, and risks.

Input Schema

NameRequiredDescriptionDefault
rootNoAbsolute project root. Required with linked worktrees; subagents must pass their own worktree root on every call.
taskYesTask description or engineering objective.
formatNoReturn plain text or structured JSON. Default: text.
presetNobalanced (default) or keyword_only for zero-provider lexical discovery.
max_filesNoMaximum ranked files to include. Default: 8.
graph_hopsNoRelated import context: 0, 1 or 2 hops. Default 1 with CONTEXTPRO_CONNECTED_CONTEXT=true, otherwise 0. Relationships are heuristic.
max_memoryNoMaximum memory hits to include. Default: 3, max: 10.
max_tokensNoFinal response budget estimated as UTF-8 bytes/4, not tokenizer tokens. Default: 3000.
include_testsNoInclude nearby tests. Default: true.
include_memoryNoInclude project memory hits. Default: true.
graph_max_filesNoMaximum additional graph-related file pointers. Default: 4.
previous_context_idNoContext ID from a previous packet you still hold; return a delta. Omit after context loss to recover full context.
include_recent_diffsNoInclude recent file-level diffs. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A4.3/5.0
Behavior4/5

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

The description adds substantial behavioral flavor by detailing the complexity of the output (e.g., 'ranked files,' 'risks'). This context goes beyond the basic safety guaranteed by the annotations (readOnlyHint: true) and gives the agent a better idea of the internal data aggregation occurring.

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?

The definition is a single, highly dense sentence that front-loads the entire value proposition. There is zero wasted language, and the structure is maximally efficient.

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?

Given the 100% schema coverage, the description provides the necessary conceptual framework and intent. It tells the agent *why* all those complex parameters (like `preset` or `graph_hops`) exist, making the definition functionally complete.

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?

Since the schema description coverage is 100%, the schema itself defines the semantics of the parameters (e.g., max_tokens, graph_hops). The description doesn't add critical meaning beyond what is structurally defined in the input schema.

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 defines the tool's function as assembling a complex, multi-component 'working set' (files, tests, memory, risks). It immediately distinguishes itself from granular sibling tools like search or grep by describing a holistic context-gathering operation.

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 sets a high-level context for usage, implying this tool is meant for high-level planning or synthesis before diving into granular tasks. While it doesn't explicitly state 'do not use search for this,' the scope of the description strongly guides the agent toward this specific, comprehensive use case.

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