Skip to main content
Glama
Sign In
Blueprint MCP

Blueprint MCP

by engincankaya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Build Blueprint Task Context

blueprint.task_context

Retrieves a deterministic set of relevant files, tests, and documents from a Blueprint artifact to provide context for a given natural-language task.

Instructions

Return a compact deterministic context slice for a natural-language task from a Blueprint output artifact.

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": {
      "blueprintArtifactId": "<blueprintArtifactId>",
      "task": "<task>"
    },
    "name": "blueprint.task_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
blueprintArtifactIdYesArtifact ID returned by blueprint.compose
taskYesNatural-language task input to route through the Blueprint graph
maxPrimaryFilesNoMaximum primary files to return
maxSecondaryFilesNoMaximum secondary files to return
maxTestsNoMaximum likely test files to return
maxDocsNoMaximum Markdown docs to recommend reading

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits like idempotency, side effects, authorization needs, or determinism beyond the term 'deterministic' which is vague. The description adds minimal value beyond the input schema.

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 description is a single sentence with no wasted words, efficiently conveying the core purpose.

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 6 parameters, the description is too brief. It fails to explain the return value structure or behavior, leaving significant gaps in understanding for an AI agent.

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%, so the schema already documents all parameters. The description adds no additional meaning beyond the parameter names and defaults, resulting in a baseline score of 3.

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 states a specific verb ('Return') and resource ('compact deterministic context slice from a Blueprint output artifact'), clearly distinguishing this tool from sibling tools like 'blueprint.compose' which likely creates a blueprint.

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?

The description provides no instructions on when to use this tool versus alternatives such as 'blueprint.scan' or 'blueprint.group', nor does it mention prerequisites or context.

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