Skip to main content
Glama

get_integration_blueprint

Read-onlyIdempotent

Retrieve a complete, AST-verified architectural reference blueprint and starter code for building a TG-Market Mini-App Storefront or Telegram Bot.

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_id": "<blueprint_id>"
    },
    "name": "get_integration_blueprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
blueprint_idYesThe blueprint template to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds value beyond them by disclosing what comes back — a complete architectural blueprint plus starter code, and that it is 'AST-verified' — which matters given there is no output schema. It omits payload size, whether code is inline versus referenced files, and any versioning, so it stops short of a 5.

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?

One sentence, front-loaded with the verb and the deliverable, with no filler or restated title. Every clause (AST-verified, blueprint, starter code, the two target platforms) carries information.

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?

For a one-parameter read-only retrieval tool with complete schema coverage and rich annotations, the description supplies the key missing piece — the nature of the returned artifact. The residual gap is the absence of any note about output size or format, which matters for a tool that returns "complete" blueprints and starter code with no output schema to describe it.

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% with a single required enum parameter whose two values are already documented in the schema. The description adds only contextual framing ("Mini-App Storefront" or "Bot") that loosely parallels the two enum values without naming or differentiating them, so the baseline of 3 applies.

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?

Specific verb ("Retrieve") plus concrete resource ("architectural reference blueprint and starter code") with the domain scope named as TG-Market Mini-App Storefront or Telegram Bot. It is clearly distinct from the sibling catalog (balance, prices, orders, endpoint specs) without needing to name one, though it never explicitly states the contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase "for building a TG-Market Mini-App Storefront or Telegram Bot" — an agent can infer it is for scaffolding/architecture-reference work, but there is no explicit when-to-use, no prerequisite, and no pointer to a sibling when a full blueprint is overkill (e.g. list_api_endpoints or get_endpoint_specification).

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.

Resources