Skip to main content
Glama

search_symbols

Find schematic components by matching reference, value, or library ID against a case-insensitive regular expression pattern.

Instructions

Find the components of a schematic whose reference, value or library ID match a pattern.

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": {
      "file_path": "<file_path>",
      "pattern": "<pattern>"
    },
    "name": "search_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYesA regular expression (no difference of case).
file_pathYesA .kicad_sch file of the project.
search_fieldsNoThe fields to search: "all" (default), "reference", "value" or "library".all

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. Beyond 'find' implying a read, it discloses nothing about match semantics, result limits, ordering, or whether the whole file is scanned; it also omits that the pattern is a regex (that detail lives only in the schema).

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?

A single well-formed sentence with the matched fields front-loaded and no filler. Nothing in it is redundant or padding.

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 output schema exists, so return values need not be described, and parameters are fully documented in the schema. However, with zero annotations a read-only search tool still benefits from stating match behavior and any result constraints, which this one-sentence description omits.

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 100%, so the schema already documents all three parameters including the search_fields enum and the case-insensitive regex rule. The description's mention of 'reference, value or library ID' loosely mirrors the enum values but adds no syntax, escaping, or scope detail beyond the schema.

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?

States a specific verb ('Find') and resource ('components of a schematic') plus the three fields matched against. The phrase 'of a schematic' implicitly separates it from library-level searches, but no sibling is named, so an agent must infer the split with search_library_symbols / search_components_by_type.

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?

Usage is only implied: an agent can deduce this searches within a project schematic file rather than a library, but the description never states when to pick this over search_library_symbols or search_components_by_type, nor any prerequisite (e.g. the file must be loaded/parsed).

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