Skip to main content
Glama

studio_ninja_type

Types text into a specified numbered field on the current Studio Ninja page, letting AI agents complete forms and data entry by field reference.

Instructions

Type text into a numbered field on the current Studio Ninja 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": "studio_ninja_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.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and leaves key traits unstated: whether existing field content is replaced or appended to, whether focus/click is required first, whether typing triggers submission or validation, and what is returned or errors on an invalid index. Only the page scope and numbering convention are conveyed.

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; the action, the target, and the scope appear immediately in an efficient order.

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

Completeness3/5

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

For a simple two-parameter typing tool with full schema coverage and no output schema, the essentials are present, but a mutation-adjacent browser action with no annotations should disclose replace-vs-append behavior and failure modes on an out-of-range field index.

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 ('Text to type' and 'Field number from the last read'). The description reinforces the numbering-from-last-read model and page scoping but adds no syntax, length limits, or special-character handling beyond the schema.

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 states a specific verb ('Type text') and target ('a numbered field on the current Studio Ninja page'), which clearly separates it from siblings like studio_ninja_click, studio_ninja_read, and studio_ninja_open. It stops short of naming or contrasting a sibling explicitly, so it is clear but not fully differentiated.

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: 'numbered field' and 'current page' suggest it must follow a read/navigation step, but the description never states when to use this instead of studio_ninja_click or what to do if the field index is unknown. There are no exclusions or prerequisites spelled out.

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