Skip to main content
Glama

ptminder_type

Type text into a numbered field on the current PTminder page to enter or update form data during PTminder tasks.

Instructions

Type text into a numbered field on the current PTminder 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": "ptminder_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 disclosure burden, and it omits key behavior: whether typing replaces or appends to existing field content, whether it dispatches keystroke/submit events, and what happens if the field number is invalid. Only the page-scope constraint is conveyed.

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 short sentence, front-loaded with the verb and target, with no filler. It is efficient, though so terse that it leaves little structure to convey the necessary caveats.

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?

For a mutating input tool with no annotations and no output schema, the definition is thin: it says nothing about post-typing effects (form submission, validation, focus change) or failure modes. The agent has to guess at the consequences of invoking it.

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%, with 'element' documented as the field number from the last read and 'text' as the string to type. The description restates 'numbered field' and adds nothing about format, length limits, or behavior for the two parameters, 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 uses a specific verb and target: 'Type text into a numbered field' scopes the action precisely and contrasts implicitly with siblings like ptminder_click and ptminder_read. It stops short of naming how it differs from those siblings explicitly, so a 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'On the current PTminder page' sets the context in which the tool applies and implies the page must already be open, but the description never states when to prefer it over e.g. ptminder_click or what to do if the field number is stale. Usage guidance is present but inferred rather than explicit.

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