Skip to main content
Glama
Wladastic

AutoProbeMCP

by Wladastic

type_text

Automate entering text into web input fields using CSS selectors, with configurable keystroke delay for precise browser form filling.

Instructions

Type text into an input field

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for the input element
textYesText to type
delayNoDelay between keystrokes in milliseconds

Implementation Reference

  • Zod schema for 'type_text' tool input validation: selector (string), text (string), delay (number, default 100)
    const TypeTextSchema = z.object({
      selector: z.string(),
      text: z.string(),
      delay: z.number().default(100)
    });
  • src/index.ts:196-218 (registration)
    Registration of the 'type_text' tool in the ListToolsRequestSchema handler, providing name, description, and inputSchema
    {
      name: 'type_text',
      description: 'Type text into an input field',
      inputSchema: {
        type: 'object',
        properties: {
          selector: {
            type: 'string',
            description: 'CSS selector for the input element'
          },
          text: {
            type: 'string',
            description: 'Text to type'
          },
          delay: {
            type: 'number',
            default: 100,
            description: 'Delay between keystrokes in milliseconds'
          }
        },
        required: ['selector', 'text']
      }
    },
  • Handler logic for 'type_text' tool: validates args using TypeTextSchema, calls currentPage.fill(selector, text) to type text into the specified input element
    case 'type_text': {
      if (!currentPage) {
        throw new Error('No browser page available. Launch a browser first.');
      }
    
      const params = TypeTextSchema.parse(args);
      await currentPage.fill(params.selector, params.text);
    
      return {
        content: [
          {
            type: 'text',
            text: `Typed "${params.text}" into element: ${params.selector}`
          }
        ]
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits such as whether the field is cleared first, how errors are handled, or if keystrokes simulate human typing. The only behavioral hint (delay) is in the schema but not mentioned in the description.

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?

The description is a single concise sentence with zero waste. It is front-loaded and efficient.

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?

Given 3 parameters, no output schema, and no annotations, the description is too minimal. It does not explain return behavior, prerequisites (e.g., element must be visible), or edge cases. More context is needed for reliable use.

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%, so the schema documents all parameters. The description adds no additional meaning beyond the schema, such as clarifying that 'type text' might append or replace existing content. Baseline score of 3 is appropriate.

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 'Type text into an input field' is a specific verb+resource pair that clearly states the tool's action. However, it does not differentiate from sibling tools like click_element, but the purpose is still distinct enough.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent would have no context for appropriate usage scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Wladastic/AutoProbeMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server