Skip to main content
Glama

blueprint_guide

Explains Blueprint screens and sign-in steps for progress notes, treatment plans, appointments, and insurance billing; call it first to orient before other tasks.

Instructions

How to work in Blueprint (work with progress notes, treatment plans, appointments and insurance billing): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Blueprint, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description bears the full disclosure burden; calling it a 'guide' and 'how to work in Blueprint' strongly implies a read-only, informational response with no side effects, and the mention of 'the sign-in link' hints at returned content. It stops short of stating that it performs no mutations, requires no auth, or whether the guidance is static or session-specific.

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?

Two sentences, front-loaded with the purpose and closing with the actionable 'Call this first' directive. The parenthetical scope list is dense but earns its space by naming the four domains covered.

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-optional-parameter guidance tool with no output schema, the description conveys enough to invoke it correctly and to know it is the entry point. What is missing is a note on what the response contains (step-by-step instructions, screen names, a URL) and how large it may be.

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 the single 'task' parameter is already documented in the schema as 'What you want done in Blueprint, in your words.' The description adds no syntax, granularity, or example for that parameter, so the baseline 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?

The description names a specific resource (an in-product guide covering screens and the sign-in link) and enumerates the functional scope: progress notes, treatment plans, appointments, and insurance billing. That is clearly distinguishable from the action-oriented siblings (click/open/read/type), though it never states what form the guidance takes (text instructions vs. links).

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?

'Call this first' gives explicit ordering guidance relative to the sibling action tools, which is exactly the routing signal an agent needs. There are no when-not conditions or stated prerequisites, so it stops short of a 5.

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