Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_getAttribute

Reads a specified attribute (href, value, aria-label, class, data-*) from an element in an active browser session using CSS, XPath, ID, or other locators.

Instructions

Read an attribute of an element (e.g. 'href', 'value', 'aria-label', 'class', 'data-*').

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": {
      "sessionId": "<sessionId>",
      "value": "<value>",
      "attribute": "<attribute>"
    },
    "name": "tb_getAttribute"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoLocator strategycss
valueYesLocator value
attributeYesAttribute name
sessionIdYesSession ID from tb_openBrowser
timeoutMsNoImplicit wait

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, 'Read' is the main behavioral signal and suggests a non-mutating operation. The description does not explain the result for a missing attribute or element, error behavior, or how the implicit wait affects lookup, and there is no output schema to fill those gaps.

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?

The single sentence is front-loaded with the operation and resource, followed by directly relevant examples. It contains no filler or unnecessary repetition of the full parameter schema.

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 clear purpose and fully documented schema are adequate for basic selection and invocation of this straightforward read tool. Completeness is limited by the absence of explicit alternative-selection guidance and unspecified return and failure behavior, which matter more because neither annotations nor an output schema are supplied.

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?

Schema description coverage is 100%, so the schema already documents all five parameters. The description adds useful concrete meaning to the generic 'Attribute name' parameter through common examples and the 'data-*' pattern, though it does not clarify attribute-name syntax or attribute-versus-property semantics.

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 clearly states the verb and resource: reading an attribute of an element. Examples such as 'href', 'aria-label', and 'data-*' clarify the target, but the description does not explicitly differentiate the tool from siblings such as tb_getText or tb_executeScript.

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?

The element-attribute context and examples imply when the tool is useful, particularly for inspecting DOM attributes. However, there is no explicit guidance on when to prefer it over alternatives, such as for visible text versus attributes or DOM attributes versus computed JavaScript properties.

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