Skip to main content
Glama

ide_search

Read-only

Searches AOT element names of a specified type across all models visible to the loaded solution, including Microsoft dependencies, using a case-insensitive regex or listing names.

Instructions

Search the artifact names of one AOT element type (Class, Table, Form, MenuItemDisplay, SecurityRole, DataEntityView, Service, ...: the Application Explorer node type) across the models visible to the loaded solution, including Microsoft dependency models, using the IDE's metadata. pattern is a case-insensitive regular expression; omit it to list names.

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": {
      "type": "<type>"
    },
    "name": "ide_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
limitNo
patternNo

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
itemsNo
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond readOnlyHint=true and openWorldHint=false, the description discloses the search scope that matters operationally: only models visible to the loaded solution, but including Microsoft dependency models, drawn from IDE metadata rather than the model database. It also makes clear the results are names, not full artifact definitions. Minor gap: the limit/truncation behavior of results is never surfaced.

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?

Front-loaded with the verb and resource in the first clause, with scope qualifiers following. It is a single dense sentence plus one short clause, and every element (element-type examples, dependency-model inclusion, regex semantics) carries information. Slightly long and clause-heavy, but no filler.

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?

With an output schema present, return-value details are not required, and annotations already cover the read-only, closed-world profile. Given a three-parameter tool, the definition covers type semantics, pattern syntax, and search scope adequately; only the limit parameter's meaning and result-truncation behavior are left unaddressed.

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 description coverage is 0%, so the description must carry parameter meaning, and it does explain two of three: `type` is defined as the Application Explorer node type with worked examples, and `pattern` is defined as a case-insensitive regex that can be omitted to list all names. The `limit` parameter (default 100, max 1000) is not mentioned anywhere, leaving result-count control undocumented in both schema and description.

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 (search) plus a precisely bounded resource (artifact names of one AOT element type) and scope (models visible to the loaded solution, including Microsoft dependency models). The parenthetical enumeration of element types and the 'Application Explorer node type' gloss make it unambiguous what is being searched, and it reads clearly as a name-search distinct from symbol-oriented siblings like ide_references or ide_definition.

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?

Gives real usage guidance for the pattern argument ('case-insensitive regular expression; omit it to list names'), which tells the agent both the filtering mode and the list-all behavior. However, it never states when to prefer this tool over siblings such as ide_project_items or ide_definition, nor any exclusions, so the when-to-use signal is only implied by the name-search framing.

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