Skip to main content
Glama
AIOProductOS

AIOProductOS Studio

Official
by AIOProductOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

studio_type

Types text keystroke by keystroke into a specified input or textarea, simulating human typing for realistic demo recordings.

Instructions

Glide to an input and type text at a human pace (keystroke by keystroke — it reads as real usage, not a paste). Use realistic demo content; whatever you type is on tape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delay_msNoPer-keystroke delay in milliseconds. Optional; default 45. Lower = faster typing (e.g. 25); higher = more deliberate.
selectorYesCSS selector of the input, textarea, or contenteditable to type into, e.g. 'input[name=email]'. Must be focusable and visible.
input_textYesThe literal text to type; it appears on tape keystroke by keystroke, so use realistic demo content (never real secrets).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.3
    • changedInput schema / properties / delay_ms / description
      Previous value: -"Per-keystroke delay (optional; default 45)."New value: +"Per-keystroke delay in milliseconds. Optional; default 45. Lower = faster typing (e.g. 25); higher = more deliberate."
    • addedInput schema / properties / delay_ms / minimum
      Added value: +0
    • changedInput schema / properties / delay_ms / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / input_text / description
      Previous value: -"Text to type."New value: +"The literal text to type; it appears on tape keystroke by keystroke, so use realistic demo content (never real secrets)."
    • changedInput schema / properties / selector / description
      Previous value: -"CSS selector of the input/textarea/contenteditable."New value: +"CSS selector of the input, textarea, or contenteditable to type into, e.g. 'input[name=email]'. Must be focusable and visible."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses that typing is keystroke-by-keystroke (not a paste) and that input appears on tape, implying recording. However, it does not detail error handling or idempotency, which is acceptable for a straightforward typing tool.

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?

Two concise sentences that immediately convey the tool's action and key behavioral nuances. Front-loaded with the verb 'glide to an input and type'—no wasted words.

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

Completeness4/5

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

For a typing tool with full schema coverage and no output schema, the description plus schema provide sufficient context. The behavior (keystroke-by-keystroke, recording awareness) is adequately described, though absence of return value mention is acceptable.

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 descriptions for all three parameters. The description adds marginal value by suggesting 'demo content' for input_text and implying human pace for delay_ms, but does not significantly enhance understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's action: typing text at a human pace keystroke by keystroke, distinguishing from pasting. The verb 'type' and resource 'input' are specific, and the context of studio tools makes differentiation from siblings natural.

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?

The description provides context (use realistic demo content, aware of recording) but does not explicitly state when to use this tool vs. alternatives. No exclusions or when-not-to-use guidance is given.

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

Deploy Server

Other Tools