Skip to main content
Glama

plancraft_click

Click a numbered element on the current Plancraft page to open pages, select offers, invoices, or contacts. Use the element number from the last read to navigate and act in the signed-in account.

Instructions

Click a numbered element on the current Plancraft 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": "plancraft_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full burden, yet it does not say what clicking actually does (navigate, submit, toggle), whether the page or element numbering changes afterward, or how an invalid/stale element number fails. The only behavioral hint is the stateful phrase "current Plancraft page".

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the action and target appear immediately. Nothing could be trimmed without losing meaning.

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 simple one-parameter action tool with no output schema, the definition is minimally viable, but with zero annotations it should at least state the expected effect of a click and whether the element index remains valid afterward. The stateful "current page" framing is present but unexploited.

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 schema already states the element number comes "from the last read". The description's "numbered element" merely restates that, adding no format or constraint detail beyond the schema. Baseline 3 applies when the schema does the work.

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?

"Click a numbered element on the current Plancraft page" names a concrete action verb (click) and a specific target (a numbered element), which is clearly distinct from reading, typing, or opening. It stops short of naming how it relates to siblings like plancraft_read, which produces the element numbers it consumes.

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 "numbered element" and "current page", suggesting the tool is used after a read to act on a listed element. There is no explicit statement of when to choose click over plancraft_type or plancraft_open, and no prerequisites such as needing a fresh read first.

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