Skip to main content
Glama

plancraft_guide

Start here to navigate Plancraft screens and sign-in, then read projects, draft offers and invoices, review overdue payments, and book working hours.

Instructions

How to work in Plancraft (read projects, draft offers and invoices, review overdue payments and book working hours): 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": "plancraft_guide"
  }
}

Input Schema

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

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?

No annotations are supplied, so the description must carry the behavioral burden. It implies a read-only informational return ("its screens and the sign-in link"), which lets an agent infer no side effects, but it never states that explicitly, nor does it say what form the response takes or whether it is a one-time read versus something re-callable. Adequate but with a real gap for an annotation-free tool.

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 compact sentence with a scannable parenthetical list of covered workflows and no filler. The strongest instruction, "Call this first," is placed at the very end rather than front-loaded, which slightly weakens the structure.

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 simple single-optional-parameter guide tool with no output schema, the description conveys what topics are covered and the calling order, which is most of what an agent needs. Only the response form and re-call behavior are left implicit.

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 a single optional 'task' parameter already fully documented in the schema. The description's listed workflows loosely suggest what belongs in that parameter, but it adds no syntax, formatting, or granularity guidance beyond the schema. Baseline 3 is appropriate when schema coverage is 100% and the description adds nothing new.

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 — Plancraft's operational knowledge — and enumerates its contents (projects, offers, invoices, overdue payments, working hours, screens, sign-in link). This clearly separates it from the sibling action tools like plancraft_click or plancraft_read. It stops short of saying outright that it returns reference/documentation text, which keeps it from a 5.

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 an explicit, unambiguous ordering instruction relative to all the other Plancraft tools, which is exactly the guidance an agent needs for a guide-type tool. It does not describe any situation where this should be skipped or re-called, but for a first-step reference tool that omission is minor.

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