Skip to main content
Glama

blueprint_open

Opens a Blueprint page in your signed-in Cloud Browser to work with progress notes, treatment plans, appointments, and insurance billing.

Instructions

Open a Blueprint page in your signed-in Cloud Browser (default https://clinician.blueprint.ai/login) to work with work with progress notes, treatment plans, appointments and insurance billing.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://clinician.blueprint.ai/login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses useful behavior ('signed-in Cloud Browser', default landing URL), but says nothing about whether navigation replaces an existing session, what happens if the browser is not already signed in, error/timeout behavior, or what the tool returns on success.

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?

A single sentence is appropriately sized and front-loads the action, but it contains a duplicated phrase ('to work with work with') and a redundant restatement of the default URL already present in the schema.

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

Completeness3/5

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

For a simple one-parameter navigation tool with no output schema, the description covers the essentials of what will be opened and where. It still leaves the session/auth precondition and post-navigation state ambiguous, which matters for an agent chaining it with click/read tools.

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?

There is one optional parameter with 100% schema description coverage; the schema already documents it and its default. The description merely repeats the same default URL, adding no new meaning about path format, absolute vs relative URLs, or allowed hosts.

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?

States a specific verb and resource ('Open a Blueprint page') plus the environment ('signed-in Cloud Browser') and enumerates the domain areas the page supports. It does not distinguish itself from siblings such as blueprint_status or blueprint_read, which could also plausibly surface Blueprint content.

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: an agent can infer this is the entry/navigation step that precedes blueprint_click, blueprint_type and blueprint_read, but the description never says so, nor does it say when to prefer blueprint_status instead.

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