Skip to main content
Glama

Whatic IC Datasheets

Search datasheets

search
Read-onlyIdempotent

Search the datasheet corpus; returns hit records (metadata + snippet, each with an opaque ref). Pass a ref list to get_segments for full content. If you already know the part number(s), prefer lookup — it fuses this search with get_segments in one call and groups full content per part. Use search when the part is unknown, or to triage snippets before pulling full content. For part-specific queries, pass scope='device:' (e.g. scope='device:NE5532') to restrict hits to that part and avoid cross-part contamination. Other scopes: 'doc:<doc_id>', 'cluster:', 'general'.

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": {
      "q": "<q>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNoMaximum number of hit records to return.
qYesFree-text query, e.g. 'input voltage noise density'.
scopeNoOptional filter restricting hits: 'device:<MPN>[,<MPN>]' (e.g. 'device:NE5532') for specific parts, 'doc:<doc_id>' for one source document, 'cluster:<name>' for a part family, or 'general' for everything.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / scope / description
      Previous value: -"Optional filter, e.g. 'device:NE5532', to restrict hits to one part and avoid cross-part matches."New value: +"Optional filter restricting hits: 'device:<MPN>[,<MPN>]' (e.g. 'device:NE5532') for specific parts, 'doc:<doc_id>' for one source document, 'cluster:<name>' for a part family, or 'general' for everything."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real behavior context beyond that: the opaque `ref` handoff to `get_segments`, the snippet-vs-full-content distinction, and the cross-part contamination risk that scope guards against. It stops short of describing ranking or pagination behavior, so not a 5.

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 purpose and return shape, then the alternative, then scope guidance — a sensible order. The scope enumeration in the final sentence is dense but each clause maps to a distinct selector, so little is wasted; a small tightening of the scope list would earn a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them briefly. Given a three-parameter, read-only search tool with a clear sibling set, an agent has everything needed to choose and call it correctly.

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 coverage is 100%, so the baseline is 3. The description earns above baseline by giving a worked scope example (`device:NE5532`) and explaining the purpose of scoping (avoiding cross-part contamination), which the schema only lists as syntax without rationale.

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 the datasheet corpus") and immediately characterizes the result shape ("hit records (metadata + snippet, each with an opaque `ref`)"). It distinguishes itself from the sibling `lookup` by naming it and explaining the different output grouping.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules: prefer `lookup` when the part number is known, use `search` when the part is unknown or to triage snippets first, and feed refs to `get_segments` for full content. It also names the exact selector for part-scoped queries, which is the main misuse risk.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources