Skip to main content
Glama

accelo_type

Types text into a numbered field on the current Accelo page, enabling AI agents to fill forms and enter data during automated workflows.

Instructions

Type text into a numbered field on the current Accelo 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": "accelo_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 supplied, the description must carry the full behavioral burden. It conveys that the tool acts on the 'current page' (statefulness) but omits key traits: whether typing replaces or appends to existing content, whether it auto-submits or triggers navigation, and what happens on an invalid field number.

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 of eleven words with no filler. The action and its scoping constraint come first, and nothing is redundant.

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?

The tool is simple (2 fully documented params, no output schema), but the absence of annotations leaves gaps the description should fill: prerequisites (a prior read/open), post-typing effects, and failure behavior. It is adequate to start a call but not to predict its side effects.

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 adds no syntax, format, or constraint details beyond the schema, so the baseline of 3 applies.

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 and resource ('Type text into a numbered field') and scopes it to the 'current Accelo page,' which distinguishes it from siblings like accelo_click and accelo_read that act on the same page. It does not explicitly name a sibling it is not, 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 schema notes the element is a 'Field number from the last read,' so the agent can infer a prior read is required. There is no guidance about when to prefer typing over accelo_click, or what to do if a field does not exist.

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