Skip to main content
Glama
Ashby MCP Server

Ashby MCP Server

ashby_type

Types text into a specific numbered field on the current Ashby page, letting you fill forms and update records by referring to fields from the last read.

Instructions

Type text into a numbered field on the current Ashby 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": "ashby_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

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. It doesn't say whether typing replaces or appends to existing text, whether it fires keystroke/submit events, whether focus is required, or what happens when the element number is stale after a page change.

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?

A single front-loaded sentence with no wasted words; the operation and target come first. It is terse to the point of thinness, but nothing is redundant or padded.

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 two-parameter browser-input tool with no output schema, the essential shape of the call is conveyed: type this text into that numbered field. However, with no annotations the definition should say more about required page state, prior-read dependency, and side effects of typing.

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 both parameters are already documented in the schema, including that 'element' is a field number from the last read. The description adds little beyond restating 'numbered field' and the page context, so the baseline 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?

States a specific verb and target: "Type text into a numbered field on the current Ashby page." The verb-plus-resource combination ('type into a field') separates it from siblings like ashby_click and ashby_read, though it never names them explicitly.

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?

No guidance on when to use this versus ashby_click (which might focus a field) or how it relates to the read/type workflow. The phrase 'current Ashby page' hints at prerequisite state but doesn't state that a prior read is required to obtain the field number.

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