Skip to main content
Glama

locate

Read-only

Searches Axure prototype widgets by name or display-text substring across pages, panel states, and repeater rows; returns paginated IDs, container paths, and text summaries for inspection or editing.

Instructions

按名称或显示文本子串搜全文档元件(可选 page/type 过滤),覆盖页面顶层与面板状态/中继器行模板内元件;返回候选(page、record、对象 id、guid、name、text 摘要、type、容器路径),默认最多 50 项,limit/offset 分页并返回 total/hasMore/nextOffset。可选传 path/rp/file 直接只读查询指定 .rp(不建 .work 副本)。把 record+id(嵌套再加 container)喂给 inspect/edit_text,或 set_widget_text 的 --record/--widget。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "locate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpNo
fileNo
pageNo
pathNo
typeNo
limitNo
queryNo
offsetNo
rpFileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description still adds real value by disclosing the default cap of 50 items, the limit/offset pagination contract with total/hasMore/nextOffset, and the important side-effect fact that passing path/rp/file queries the .rp directly without creating a .work copy.

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?

Densely packed but front-loaded: purpose first, then coverage scope, then return shape, then pagination, then the file-mode caveat, then the follow-up handoff. Every clause carries information, though the single long sentence structure makes it slightly harder to scan than a bulleted form would.

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 9-parameter read tool with no output schema, the description supplies the candidate field list (page, record, object id, guid, name, text summary, type, container path), the pagination metadata, and how to consume the result downstream — enough for an agent to call it and use the output. Only the unidentified query/rpFile parameters leave a small hole.

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 0%, so the description carries the burden and mostly does: it maps page, type, limit/offset, path/rp/file to their meanings and states the default limit and the read-only file behavior. Gaps remain — the substring parameter is described semantically but never named 'query', rpFile is undocumented, and no limit bounds (1–200) or type value space is given.

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?

States a specific verb and resource — search all-document widgets by name or display-text substring — and immediately scopes it further with optional page/type filters and the fact that it spans page top level, panel states, and repeater row templates. An agent can tell this is a discovery/lookup tool, not a mutation tool, without opening the schema.

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?

Explains the input needed (name or text substring) and gives an explicit downstream handoff: feed record+id (plus container when nested) to inspect/edit_text or to set_widget_text's --record/--widget. It also notes the read-only direct .rp option. It does not state when NOT to use it or name a competing search tool, so it stops short of a full 5.

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