Marcora

get_community_blueprint_details

Read-onlyIdempotent

Get the full details for a specific community blueprint, including its complete content (markdown), content description/style guide, and contributor information.

Use the 'id' (blueprint_exchange_id) returned by list_community_blueprints. The 'content' field contains the full example document in markdown. The 'content_description' describes the template structure and style guidelines.

Pass the 'id' to import_community_blueprint to add this blueprint to the current team.

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": {
      "blueprint_exchange_id": "<blueprint_exchange_id>"
    },
    "name": "get_community_blueprint_details"
  }
}

Input Schema

Name	Required	Description	Default
`blueprint_exchange_id`	Yes	The UUID from the `id` field of a list_community_blueprints result — the identifier of an entry in the shared community blueprint library. The `slug` returned alongside it will not resolve; use `id`. Entries that have been retired from the library return a not-found error. Pass the same value to import_community_blueprint to copy the blueprint into your team.

Output Schema

Name	Required	Description
`id`	Yes	Blueprint exchange ID. Pass to import_community_blueprint.
`name`	Yes	Blueprint name.
`slug`	No	URL-friendly identifier.
`content`	Yes	Full example document content in markdown.
`summary`	No	What this blueprint produces.
`visibility`	No	Exchange visibility status (e.g. public).
`is_featured`	No	Whether this blueprint is featured by Marcora.
`contributor_name`	No	Name of the blueprint creator.
`input_instructions`	No	Guidance for what context to provide when generating from this blueprint.
`content_description`	No	Template structure and style guidelines.
`contributor_company`	No	Company of the blueprint creator.
`contributor_job_title`	No	Job title of the blueprint creator.
`suggested_content_type`	No	Suggested content type name for this blueprint.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing what is actually returned (full markdown document, style guide) and confirming the id-keyed lookup. It does not mention failure modes in the description itself (retired entries), though the schema does.

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 short front-loaded paragraphs: what it returns, how to obtain the id and what the fields mean, and the follow-up tool. No filler, and the return-field explanation is placed before the workflow hint.

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?

A single-parameter read tool with full schema coverage, rich annotations, and an output schema. The description covers purpose, input provenance, return content semantics, and next-step chaining — nothing an agent needs to invoke it correctly is missing.

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% and already explains that the UUID must come from list_community_blueprints' `id` field and that `slug` will not resolve. The description restates the same sourcing guidance, adding confirmation but little new meaning, so the baseline 3 applies.

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 ('Get the full details for a specific community blueprint') and enumerates what comes back: markdown content, content description/style guide, and contributor info. Naming 'community blueprint' plus the sibling references (list_community_blueprints, import_community_blueprint) separates it from the team-scoped get_blueprint.

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 an explicit chained workflow: obtain the 'id' from list_community_blueprints, call this tool, then pass the same id to import_community_blueprint. Both the prerequisite and the downstream action are named, leaving nothing to inference.

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

All Marcora tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?