Skip to main content
Glama

Read the blueprint method

blueprint_method
Read-only

The Project Blueprint method (free, no passport needed): six planning stages (concept, features, pages, database, tech_spec, tasks), each with instructions, a JSON Schema and a worked example. You plan with your own model. Buy project-blueprint, after your human says yes, to get every stage checked (your database schema really runs on PostgreSQL), a task list you tick off, and a plan page for your human; your owner's first one is free. Without stage: all six and how to buy; with stage: just that one.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stage": "concept"
    },
    "name": "blueprint_method"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNoStage name, in order: concept, features, pages, database, tech_spec, tasks.
passport_tokenNoNot needed on this public tool; accepted and ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "stage": "concept"
      +  }
      +]
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / passport_token
      Added value: +{
      +  "description": "Not needed on this public tool; accepted and ignored.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / stage / description
      Added value: +"Stage name, in order: concept, features, pages, database, tech_spec, tasks."
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add context — and it does: cost is zero, no passport is required, passport_token is accepted and ignored, and the response content per mode is sketched out. However, the description is heavily freighted with promotional upsell copy rather than operational detail such as response size or rate limits for this read endpoint.

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?

The core purpose is front-loaded in the first clause, but the whole definition is a single run-on sentence stitched together with parentheticals, a sales pitch ('your owner's first one is free') and asides that do not help an agent invoke the tool. It is readable but not efficiently structured.

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

Completeness4/5

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

There is no output schema, so the description carries the burden of describing returns — and it does, listing the six stage names, what each stage contains (instructions, JSON Schema, worked example), and what the no-stage call returns. Only minor gaps remain, such as the shape/size of the returned example payloads.

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

Parameters4/5

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

Schema coverage is 100%, so the enum and the passport_token description are already documented, making 3 the baseline. The description adds genuine meaning beyond the schema by spelling out the omit-behavior ('Without stage: all six and how to buy; with stage: just that one'), which the schema alone does not convey for an optional parameter.

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?

The description names a specific resource (the Project Blueprint method) and enumerates its contents: six planning stages with instructions, a JSON Schema and a worked example. It also clarifies the two invocation modes (all stages vs. a single stage), which distinguishes its behavior from adjacent blueprint tools, though it never explicitly contrasts itself with siblings like blueprint_put_stage or blueprint_tasks.

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?

It states the operating context clearly: 'You plan with your own model' and the tool is 'free, no passport needed,' while the paid, human-approved path is routed to a differently named purchase action ('Buy project-blueprint, after your human says yes'). That gives a usable when-to-use signal plus a handoff condition, but it never explicitly says when NOT to use this tool or which sibling to pick for stage mutation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.