Skip to main content
Glama
Sign In
Project Brain

Project Brain

by Perlitten
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Prepare task context

prepare_task_context
Read-only

Builds bounded runtime context slices for AI coding agents from a task description, using codebase retrieval and graph navigation; durable packs need an explicit deep job.

Instructions

Returns bounded runtime slices; durable packs are an explicit deep job.

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": {
      "task_description": "<task_description>"
    },
    "name": "prepare_task_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_pathNo
task_descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.2

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a real behavioral trait beyond that: output is 'bounded' and non-durable ('runtime slices'), with durable artifacts deferred to a separate deep job. That is useful context, though nothing about auth, limits, or return shape is given.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted words and the runtime/durable distinction is front-loaded. However, the brevity comes at the cost of clarity — the sentence is under-specified rather than genuinely concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameter documentation, the description carries the full burden and falls short. An agent still doesn't know what 'slices' contain, how large 'bounded' is, or what the required task_description produces.

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 0% and the description says nothing about either parameter. The names (task_description required, repo_path optional) are fairly self-explanatory, but the description makes no attempt to explain what a repo_path does or how the task description is used, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it 'Returns bounded runtime slices', which is opaque jargon rather than a clear verb+resource statement of what context is prepared for a task. The only concrete signal is the contrast with 'durable packs' / 'explicit deep job', which hints at sibling differentiation (prepare_deep_context) but never states the tool's actual purpose.

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

Usage Guidelines2/5

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

It gestures at an alternative ('durable packs are an explicit deep job'), implying the deep-context tool handles heavier work, but never explicitly says when to choose this tool over prepare_deep_context or any other sibling. An agent must infer the routing rule from a cryptic clause.

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