Skip to main content
Glama

skiddle_type

Types text into a specified numbered field on the current Skiddle page to enable form entry during promoter workflows.

Instructions

Type text into a numbered field on the current Skiddle 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": "skiddle_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 provides almost none. It does not say whether text is appended or replaces existing content, whether typing submits/submits-on-enter, what happens with an out-of-range element number, or whether a re-read is needed afterward.

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 zero waste, though it is so terse that brevity comes at the cost of missing behavioral detail rather than achieving density.

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 browser-interaction tool with no annotations and no output schema, an agent still lacks critical context: whether the field must be visible/enabled, what the call returns, and how to recover from a stale field number. The description leaves these to guesswork.

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 the schema already defines both 'text' and 'element'. The description's phrase "numbered field" corroborates the element parameter but adds no format, constraints, or edge-case semantics beyond it.

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 resource ("a numbered field on the current Skiddle page"), which distinguishes it from read/click/open siblings. It stops short of naming an alternative but the action is unambiguous.

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: the field must already be numbered, which ties it to a prior read, and the schema field description confirms "Field number from the last read." There is no explicit guidance on when to reach for this versus skiddle_click or skiddle_read.

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