Skip to main content
Glama
Sign In
lynxprompt-mcp

lynxprompt-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Get blueprint

get_blueprint
Read-onlyIdempotent

Read an accessible blueprint's full content and checksum before updating, then pass the checksum as expected_checksum to avoid overwriting concurrent edits.

Instructions

Read one blueprint the token can see, including its full content and its content_checksum: your own, your team's, or a public one found with search_blueprints. Call it before update_blueprint and pass content_checksum as expected_checksum, so an edit made elsewhere in the meantime is not overwritten. Only the owner can update or delete a blueprint. For a public blueprint of someone outside your team, repository_path is only the file name.

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": {
      "id": "<id>"
    },
    "name": "get_blueprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBlueprint id from list_blueprints or search_blueprints, e.g. bp_clx1abc.

Output Schema

NameRequiredDescriptionDefault
successNo
blueprintNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the safe-read profile (readOnly, idempotent, non-destructive); the description adds the non-obvious visibility model (own, team, or public blueprint), the ownership rule governing update/delete, and a data quirk — for a public blueprint outside the team, repository_path is only the file name. That is real behavior the annotations cannot convey.

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?

Three sentences, purpose front-loaded, then the safe-edit workflow, then the ownership and path caveats. No filler and nothing repeated from the schema header.

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?

An output schema exists, so return values need no prose explanation, yet the description still notes what content and checksum mean for downstream use. Visibility, permissions, and the public-repo path caveat round out everything an agent needs to call this correctly.

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?

The single parameter has 100% schema description coverage, including where the id comes from and its format example, so the schema carries the load. The description's only added semantic content is the expected_checksum handoff, which concerns another tool's parameter rather than this one's id.

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?

States a specific verb and resource ('Read one blueprint') plus the scope of what is returned ('full content and its content_checksum'), and distinguishes itself from search_blueprints by name. An agent can separate it from list_blueprints/get_hierarchy without opening any schema.

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?

Gives explicit sequencing guidance: 'Call it before update_blueprint and pass content_checksum as expected_checksum' with the reason (avoid clobbering concurrent edits), and routes discovery to search_blueprints. This is when-to-use plus how-to-chain, not just 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