Skip to main content
Glama
Sign In
neko-browser

neko-browser

by aliksir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

neko_get_attribute

Retrieve attribute values from a webpage element using its index. Optionally specify an attribute name to get a single value, or omit to get all attributes.

Instructions

Get attribute value(s) of an element. Returns all attributes if no name is specified.

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": {
      "index": "<index>"
    },
    "name": "neko_get_attribute"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoAttribute name (omit to get all attributes)
indexYesElement index from neko_get_state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It indicates a read operation but does not disclose error behavior, permission requirements, or return format. Adequate but not thorough.

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?

Two sentences with no waste, front-loaded with verb and resource. Every sentence is informative and necessary.

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

Completeness4/5

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

For a simple read tool, description covers essential behavior. However, lack of output schema and missing return format details slightly reduce completeness. Adequate for straightforward use.

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 coverage is 100%, establishing baseline 3. Description adds value by clarifying the behavior when name is omitted ('returns all attributes') and overall purpose, exceeding the baseline.

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?

Description clearly states the action 'get attribute' on an element, and differentiates itself from siblings like neko_get_state and neko_get_html by specifying the resource 'attributes'.

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

Usage Guidelines4/5

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

Implies when to omit the name parameter to get all attributes, but does not explicitly state when to use this tool over siblings. However, sibling names are distinct and context clues are sufficient.

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