Skip to main content
Glama

zenoti_type

Types text into a chosen numbered field on the current Zenoti page, enabling agents to fill form inputs during Zenoti workflows.

Instructions

Type text into a numbered field on the current Zenoti 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": "zenoti_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

C2.9/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 and it does very little: it does not say whether existing text is replaced or appended, whether typing triggers change/blur/submit events, whether focus or a wait is performed, or what happens with an invalid element number. Only the 'current Zenoti page' scope is disclosed.

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 zero filler that states the action and the target. Nothing is repeated or wasted.

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 UI-automation input tool with no annotations and no output schema, the agent needs to know side effects (replace vs append, event firing, waiting, error behavior) — none of which is present. The schema fully covers the two parameters, but the behavioral surface of a typing action is undocumented.

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%, with both `el text` and `element` documented (including the 'field number from the last read' provenance and minimum 1), so the baseline of 3 applies. The description restates the same 'numbered field' concept without adding format, length, or clear-before-type semantics.

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?

States a specific verb (type text) and target (a numbered field on the current Zenoti page), which is enough to distinguish it from zenoti_click and zenoti_read in practice. It stops short of naming those siblings explicitly, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites (e.g., that a field number must first be obtained via a read), and no mention of alternatives such as zenoti_click. The only hint of workflow ordering — 'numbered field' — is left implicit and is really carried by the schema's 'Field number from the last read.'

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