Skip to main content
Glama

library_search

Read-only

Search the installed Proteus .LIB device index by query to find components without mouse navigation or screenshots; results show device availability, not native placement support.

Instructions

Search the actual installed Proteus .LIB device index without mouse or screenshots. Finding a device does not imply native placement support.

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": {
      "query": "<query>"
    },
    "name": "library_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by clarifying that results come from the actually installed .LIB index with no mouse/screenshot interaction, and that a hit is not a placement guarantee. It says nothing about result volume, ordering, or how matching works.

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?

Two tight sentences with the core action front-loaded and the caveat following it. No filler, though the second sentence is telegraphic enough that its intent ('check native support separately') takes a moment to decode.

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?

For a two-parameter read-only lookup with no output schema, the safety and provenance story is adequate, but the definition leaves out search-matching behavior and the meaning/effect of 'limit', both of which an agent needs to call it correctly the first time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 full burden for both parameters and adds nothing: it never explains what 'query' matches (prefix, wildcard, exact part number) or what 'limit' bounds. With no coverage in the schema and no compensation in the description, an agent must guess the search syntax.

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?

The description names a specific verb ('Search') and a specific resource ('the actual installed Proteus .LIB device index'), and the qualifier 'actual installed' implicitly contrasts it with a non-installed catalog such as catalog_list. It stops short of naming the sibling it differs from, so the differentiation relies on inference.

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 implied rather than stated: search this when you need to locate a device in the installed library. The caveat 'Finding a device does not imply native placement support' is a useful warning that routes the agent elsewhere before acting, but no explicit alternative (e.g. native_check) or when-not condition is given.

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