Skip to main content
Glama
munimtechnologies

Computer Use

by munimtechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Select text

select_text
Idempotent

Select a specific character range within a text element to copy or replace only that portion, leaving the rest unchanged.

Instructions

Select a character range inside a text element through the accessibility API, for example to copy part of a value or to replace just that part with type_text. Defaults to selecting from start to the end of the value. Use set_value to replace the whole value instead. Only the selection changes; the text is not modified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startNoZero-based character offset to start the selection at (default 0)
lengthNoNumber of characters to select (default: through the end of the value)
element_idYesText element to select in, from get_app_state

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedInput schema / properties / element_id / description
      Added value: +"Text element to select in, from get_app_state"
    • changedInput schema / properties / length / description
      Previous value: -"Characters to select (default: to end)"New value: +"Number of characters to select (default: through the end of the value)"
    • changedInput schema / properties / start / description
      Previous value: -"Start offset (default 0)"New value: +"Zero-based character offset to start the selection at (default 0)"
  2. First observedv0.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds valuable behavioral details: the default selection extends from start to end, and 'Only the selection changes; the text is not modified.' This clarifies the operation's state-changing but non-destructive nature, which is exactly the kind of context annotations alone do not provide.

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?

Three sentences, each earning its place: mechanism and examples in the first, default behavior in the second, and an explicit alternative and side-effect clarification in the third. No filler or redundant restating of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter tool with complete schema coverage and clear annotations, the description covers what the tool does, why to use it, how it behaves by default, what it does not do, and which sibling to use instead. The absence of an output schema is not a meaningful gap here because the operation's result is a selection state, not a data-returning query.

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

Parameters4/5

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

The schema already documents all three parameters at 100% coverage, so the baseline is 3. The description adds value by explaining the practical purpose of the parameters ('copy part of a value', 'replace just that part with type_text') and reinforcing defaults ('Defaults to selecting from start to the end of the value'). This upgrades the score to 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise action ('Select a character range inside a text element through the accessibility API') on a clear resource, and immediately differentiates itself from related tools by mentioning set_value for whole-value replacement and type_text for partial replacement. This is a specific verb+resource combination that an agent can distinguish from all sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the workflow context: copying part of a value or replacing just that part with type_text. It also gives a direct alternative: 'Use set_value to replace the whole value instead.' This tells the agent exactly when to use this tool versus its siblings.

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

Deploy Server

Other Tools