Skip to main content
Glama

blueprint_click

Selects a numbered element on the current Blueprint page to navigate or trigger the corresponding action in a signed-in clinician workflow.

Instructions

Click a numbered element on the current Blueprint page.

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": {
      "element": "<element>"
    },
    "name": "blueprint_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it never says what a click does (navigate, submit, expand, trigger a form), whether it is reversible, or how stale element numbers fail. For an action tool with zero annotation coverage, that is a substantial gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the verb and the scoping constraint front-loaded, and no redundant wording. Its terseness is close to under-specification, but nothing present is wasted.

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 one-parameter action tool with no output schema, the essentials are largely covered by the schema, but the absence of annotations means the description should explain click side effects and failure modes and it does not.

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 is fully documented in the schema ("Element number from the last read"), so schema coverage is 100% and the baseline of 3 applies. The description adds no extra meaning about valid ranges or staleness beyond that.

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 gives a specific verb plus resource ("Click a numbered element") qualified by scope ("on the current Blueprint page"), which clearly separates it from read/type/close siblings. It stops short of naming any sibling as the alternative, so an agent must infer the boundary itself.

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

Usage Guidelines2/5

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

"On the current Blueprint page" hints that a page must be open, but nothing states when to click versus type/read/close, and no exclusions or prerequisites are given. The critical precondition (element numbers come from the last read) exists only in the schema, not the description.

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