Skip to main content
Glama

blueprint_status

Verify your Cotlet.dev account, credits, and Blueprint connection are ready before running Blueprint actions.

Instructions

Check that your Cotlet.dev account and Blueprint are ready: account, credits and Blueprint connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does name the three things inspected (account, credits, Blueprint connection), which tells the agent what this probes, but it says nothing about whether it makes a network request, whether it consumes or reports credits, what happens on partial failure (account OK but Blueprint disconnected), or what the result looks like.

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?

A single front-loaded sentence with the verb first and the three checked items in a colon list. No filler, though the phrasing is slightly compressed to the point of being clipped ('Blueprint are ready').

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 zero-parameter, side-effect-free probe with no output schema, the missing piece is what the caller gets back — is it a boolean, a status object with credit counts, or errors per check? The description also doesn't say whether this is a prerequisite for the sibling Blueprint tools, which is the main decision an agent would need it for.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The brief enumeration of checked areas is a reasonable stand-in for argument detail.

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?

A specific verb ('Check') plus the resource being checked (Cotlet.dev account, credits, Blueprint connection). It is clearly a readiness/diagnostic probe rather than an action, which implicitly separates it from the sibling verbs (open, click, close, read, type, guide), though it never names those siblings to draw the contrast explicitly.

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?

'Check that ... are ready' hints the tool belongs before other Blueprint operations or as a troubleshooting step, but this is only implied. There is no explicit when-to-use, no when-not-to-use, and no statement of whether a caller should run this before or after the sibling tools.

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