Skip to main content
Glama

bolster_type

Types text into a numbered field on the current Bolster page, letting you fill estimates, proposals, or scheduling forms by field reference.

Instructions

Type text into a numbered field on the current Bolster 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": "bolster_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.2/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, and it discloses little beyond the action itself. It does not say whether typing appends to or replaces existing field content, whether it triggers submit/blur events, what happens on an invalid field number, or what the result looks like.

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, and the action is stated first. It is efficient, though that brevity comes partly at the cost of the behavioral detail noted above.

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 action with no nested objects or output schema, the definition is minimally adequate: an agent knows what to send. It is incomplete on the mutation semantics (replace vs append, side effects) that matter for an unannotated write tool.

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 in the schema. The description only reinforces that 'element' refers to a numbered field on the current page; it adds no format, ordering, or edge-case semantics beyond that baseline.

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 resource ('Type text into a numbered field') and scopes it to 'the current Bolster page,' which separates it from bolster_read or bolster_click. It is clear what the tool does, though it never explicitly contrasts itself with the input-oriented sibling bolster_click.

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 phrase 'numbered field from the last read' hints that a prior bolster_read must supply the index, but there is no explicit when-to-use, prerequisites, or when-not-to-use guidance. An agent can infer the workflow but must do the work itself.

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