Skip to main content
Glama

Search

search
Read-onlyIdempotent

Keyword search across the trust center content and accessible documents. Returns matching passages with their source. Use short keywords (e.g. "encryption at rest", "backup", "MFA"), not full sentences. Without trust_center, searches the trust centers where you are an approved visitor and those whose company name or domain appears in the query (e.g. "Acme encryption at rest").

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": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 8)
queryYes
languageNoOptional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
trust_centerNoTrust center id (from list_trust_centers), its domain or the exact company name. Optional for search.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: results are passages with provenance, and access is implicitly permission-scoped to trust centers where the caller is an approved visitor, with company-name/domain matching in the query widening scope.

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?

Three sentences, front-loaded with the core action, then query formatting, then scope fallback. Every sentence carries information an agent needs to call the tool correctly; nothing is restated from the schema or annotations.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description handles the two things most likely to cause a bad call (long natural-language queries and omitted trust_center) but says nothing about how limit interacts with passage-level results or multi-trust-center result ordering.

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?

With 75% schema coverage the baseline is already decent, and the description adds meaning the schema lacks: query should be short keywords, and omitting trust_center triggers a specific implicit-scope behavior plus name/domain matching. The limit parameter's effect on result volume is left entirely to the schema.

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 ('Keyword search across the trust center content and accessible documents') and adds the return shape ('matching passages with their source'). This distinguishes it from document-listing siblings like list_documents and full-text siblings like get_document_text without needing to open a 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?

Gives concrete usage guidance: use short keywords like 'encryption at rest' or 'MFA' rather than full sentences, and explains the default scope when trust_center is omitted (approved-visitor trust centers plus those named in the query). It stops short of naming an explicit alternative such as get_document_text for full-document retrieval, so there are no stated exclusions.

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