Skip to main content
Glama
docmancer

docmancer

Official
by docmancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

context_projection

Read-onlyIdempotent

Render and preview the exact bounded context text an agent receives for the current revision to verify integration behavior before installation.

Instructions

READ-ONLY: render the actual bounded context text one named agent would receive, linked to the current revision. Local disk read that renders without writing, refreshing, or delivering anything, so it is safe to preview repeatedly. This is the show-me-the-content question, so use it to check what an agent will actually see before installing or debugging an integration. It is one of three context tools: context_status reports the revision and its freshness, and context_delivery reports whether each agent is receiving it. Refresh, rollback, adopt, and retire are human-only CLI or local-web operations. Parameters: agent is the required target agent identifier, and the projection is shaped for that agent's integration; token_budget bounds the rendered size in approximate tokens (default 2000), so raising it returns more content and lowering it truncates by priority; project_path project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project. Returns an object with the rendered projection text and the revision it was built from.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentYesTarget agent identifier used to shape and attribute the result. Defaults are tool-specific.
project_pathNoProject root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project.
token_budgetNoApproximate maximum token size of the returned context projection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.16
    • changedInput schema / properties / agent / description
      Previous value: -"Target agent identifier, such as claude-code or cursor, used to shape and attribute the result. Defaults are tool-specific."New value: +"Target agent identifier used to shape and attribute the result. Defaults are tool-specific."
  2. Changed3 schema fields changedv0.9.13
    • addedInput schema / properties / agent / description
      Added value: +"Target agent identifier, such as claude-code or cursor, used to shape and attribute the result. Defaults are tool-specific."
    • addedInput schema / properties / project_path / description
      Added value: +"Project root whose memory tree the operation applies to. Omit it to use the machine-wide tree, and always omit it when this server was started pinned to a project."
    • addedInput schema / properties / token_budget / description
      Added value: +"Approximate maximum token size of the returned context projection."
  3. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

The description fully discloses side effects: 'READ-ONLY', 'Local disk read that renders without writing, refreshing, or delivering anything', and 'safe to preview repeatedly'. This goes beyond the annotations (readOnlyHint, idempotentHint, destructiveHint) by explaining what is NOT done and the practical implication of safety. No contradiction exists.

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?

The description is well-structured and front-loaded with the safety and purpose, then usage context, then parameter walkthrough. It is longer than strictly minimal but every sentence contributes either to distinguishing the tool or to parameter semantics. Slightly verbose, but appropriate for the tool's complexity and sibling set.

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?

The description covers the tool's purpose, safety profile, relationship to two sibling tools, human-only alternatives, all parameters, the return object ('rendered projection text and the revision it was built from'), and project scope handling. Given the tool's moderate complexity and minimal schema/annotations, this is fully complete.

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

Parameters5/5

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

Even though schema description coverage is 100%, the description adds meaningful behavioral detail for token_budget ('raising it returns more content and lowering it truncates by priority'), project_path ('always omit it when this server was started pinned to a project'), and clarifies agent as the required target. These nuances are not present in the schema descriptions.

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 uses a precise verb+resource ('render the actual bounded context text one named agent would receive') and explicitly distinguishes itself from sibling tools by stating what context_status and context_delivery do differently. It clearly identifies this as the 'show-me-the-content' tool.

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?

It provides explicit when-to-use guidance ('check what an agent will actually see before installing or debugging an integration') and when-not-to-use guidance by noting that refresh/rollback/adopt/retire are human-only CLI/local-web operations. It also names the alternative tools for revision freshness and delivery status, making the decision matrix clear.

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