Skip to main content
Glama

plancraft_open

Open a Plancraft page in your signed-in Cloud Browser to manage projects, draft offers and invoices, review overdue payments, and book working hours.

Instructions

Open a Plancraft page in your signed-in Cloud Browser (default https://plancraft.com) to work with read projects, draft offers and invoices, review overdue payments and book working hours.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://plancraft.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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, and it does disclose two useful traits: the browser session is already signed in, and there is a default destination. It does not say whether navigation reuses or replaces the current page, what happens with an invalid or external URL, or whether the page content is returned to the caller — meaningful gaps for a browser-navigation 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 sentence, front-loaded with the action and its execution environment, followed by concrete example workflows. The workflow list is slightly long, but each item conveys what the page enables, so nothing is clearly wasteful.

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, non-destructive navigation tool with no output schema, the description covers the essential 'what' and the authenticated context. It still leaves open what the caller gets back after opening and how the browser session state relates to the follow-up click/type/read tools, which an agent would need in order to chain calls confidently.

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?

Schema coverage is 100% and the single parameter already documents its own default (https://plancraft.com). The description restates that same default, adding no new meaning about accepted URL forms or constraints, so the baseline 3 applies.

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 verb and resource — 'Open a Plancraft page in your signed-in Cloud Browser' — plus the default target URL. That is enough to separate it from the sibling action tools (click, type, read, close), even though no sibling is named 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?

Usage is only implied through the list of downstream activities (read projects, draft offers and invoices, review overdue payments, book working hours), which suggests this is the entry/navigation step before those workflows. There is no explicit 'use this when...' framing, no stated alternative (e.g. when to use plancraft_read or plancraft_status instead), and no prerequisites or exclusions.

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