Skip to main content
Glama

type_text

Types a literal string verbatim by sending Unicode packets, so an active Chinese IME cannot convert a URL into pinyin composition.

Instructions

Type a literal string verbatim. Characters are sent as Unicode packets, so an active Chinese IME cannot swallow a URL into pinyin composition.

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": {
      "text": "<text>"
    },
    "name": "type_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
dry_runNo
intervalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It usefully discloses that characters go out as Unicode packets and bypass a Chinese IME, but it never says that dry_run defaults to true, meaning the tool does not actually type unless the caller opts in, nor does it explain what interval controls or what happens on failure.

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?

Two sentences, front-loaded with the core action, and the IME sentence is a concrete operational detail rather than filler. Nothing is padded, though the brevity comes at the cost of the missing parameter information noted above.

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?

With no annotations, no output schema, and zero parameter documentation, the description should have covered the safety-relevant dry_run default and the pacing parameter. It instead spends its second sentence on one narrow IME scenario, leaving an agent unable to predict that a call may do nothing by default.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and does not. Neither text, dry_run (a default-true boolean that inverts the expected effect of calling a typing tool), nor interval is explained anywhere, and the dry run default is precisely the kind of meaning the description should surface.

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 names a specific verb and resource ("Type a literal string verbatim") and the word "verbatim" signals literal, non-interpreted input. It does not distinguish itself from the sibling browser_type, so an agent cannot tell from this text which typing tool to pick.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as browser_type, despite obvious overlap. The IME sentence implies a use case but is framed as mechanics rather than a selection rule.

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