Skip to main content
Glama
Sign In
locator-mcp

locator-mcp

by Eswarr11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_registry_keys

Retrieve a lightweight list of element keys from a scan registry, including tagName, testId, and confidence for efficient locator analysis.

Instructions

Return a lightweight list of element keys with tagName, testId, and confidence — much smaller than the full registry.

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": {
      "scanName": "<scanName>"
    },
    "name": "get_registry_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
scanNameYesRegistry filename without .json.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden. It only describes the return content but fails to disclose any behavioral traits such as read-only nature, performance characteristics, or potential side effects.

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 description is a single sentence that is front-loaded with the action and keeps all information relevant. No wasted words.

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?

While the description mentions the fields returned, it lacks details on the structure (e.g., array of objects?), pagination, or error conditions. Given no output schema, more completeness would be helpful.

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% for the single parameter scanName, with a clear description. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states it returns a lightweight list of element keys with specific properties (tagName, testId, confidence) and contrasts it with the full registry, effectively distinguishing from sibling tools like get_registry.

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?

The description implies when to use this tool (when a lightweight list is needed instead of the full registry) but does not explicitly exclude use cases or mention alternatives beyond the contrast.

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