Skip to main content
Glama

plancraft_status

Verify your Cotlet.dev account, credit availability, and Plancraft connection before using the integration.

Instructions

Check that your Cotlet.dev account and Plancraft are ready: account, credits and Plancraft 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": "plancraft_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/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 does convey that this is a non-mutating diagnostic and names the three checks performed, but it says nothing about the response shape, whether failures surface as errors or as status fields, or whether any authentication prerequisite exists beyond the account being checked.

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 no filler. It is mildly redundant in restating 'account' from the first clause in the enumeration, but that repetition also disambiguates the three checks.

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 zero-parameter diagnostic with no output schema, the description covers the essential scope by naming the three checks. The main remaining gap is what the result looks like (per-check status vs. a single verdict) and whether remediation guidance is returned.

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 no parameter semantics to explain and the baseline applies. The description correctly omits any parameter discussion rather than padding with irrelevant 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?

States a specific verb ('check') and a defined readiness resource, then enumerates the three things verified: account, credits, and Plancraft connection. That is enough to distinguish it from the sibling action tools (click, open, read, type), though it never explicitly says so.

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 'ready' – an agent can infer this is a pre-flight check before calling the plancraft_* action tools, but the description never states when to call it, whether it is required before acting, or what to do if a check fails.

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