Skip to main content
Glama

plancraft_type

Types text into a numbered field on the current Plancraft page, letting you fill in offers, invoices, or contacts by targeting the field number from your last read.

Instructions

Type text into a numbered field 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>",
      "text": "<text>"
    },
    "name": "plancraft_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a write/input operation. It does not say whether existing field content is replaced or appended, whether typing submits the form, what happens on an out-of-range element number, or whether focus is required — all material for an agent performing UI input.

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 or redundancy. It is efficient, but the brevity leaves the behavioral and prerequisite gaps noted above rather than structuring them into the definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only source of behavioral information for a mutating UI action, and it omits replace-vs-append semantics, error behavior for invalid field numbers, and the result of the action. For a two-parameter input tool this is thin.

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 description coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description adds only the framing that the integer refers to a field number on the current page; it adds nothing about text encoding, multiline input, or length limits.

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?

"Type text into a numbered field" gives a specific verb (type) and resource (numbered field), and "on the current Plancraft page" scopes the target. It is distinguishable from plancraft_click and plancraft_read by the action verb alone, though it never names a sibling 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?

"Numbered field" plus the schema note "Field number from the last read" implies the read-then-type workflow, and "current page" implies a page must already be open. However, no prerequisite or when-not-to-use condition is stated in the description itself, so the sequencing must be inferred.

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