Skip to main content
Glama

Search the site

search_site
Read-onlyIdempotent

Search IP Computers's Hebrew guides, product and service pages (SentinelOne EDR, ransomware, backup, RMM, VPS, firewall monitoring). Returns matching pages with title, URL, summary and a relevance score.

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_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results, 1 to 20.
queryYesKeywords in Hebrew or English, for example "כופרה", "SentinelOne install", "גיבוי 365".

Output Schema

NameRequiredDescriptionDefault
totalYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds the topical scope and the returned fields (title, URL, summary, relevance score), but that return detail is also captured by the existing output schema, and it says nothing about result limits, ranking behavior, or empty-result handling.

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?

Two sentences, front-loaded with the resource being searched and followed by the return shape; no filler, no repetition of the title.

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 only two parameters, full schema coverage, an output schema and annotations, the description is nearly complete. The only wobble is the phrase 'Hebrew guides' alongside schema examples permitting English keywords, which leaves the content-language relationship slightly ambiguous.

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 both query and limit are already fully documented, including length bounds and Hebrew/English examples. The description's list of product domains offers only marginal help in query formulation and adds nothing about the limit parameter, so the baseline 3 applies.

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?

The description gives a specific verb ('Search') and a precisely bounded resource: Hebrew guides plus product/service pages, with the topical domains named (SentinelOne EDR, ransomware, backup, RMM, VPS, firewall monitoring). This is clearly distinguishable from the sibling quote/product/contact tools without opening any schema.

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 by the topical scope; there is no explicit statement of when to prefer this tool over siblings such as list_products or get_product, nor any exclusions. An agent can infer it is the site-wide discovery entry point, but the definition never says so.

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