Skip to main content
Glama

Search public web

exim__web__search
Read-only

Returns up to 10 public page titles, URLs and snippets in relevance order.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text (1 to 300 characters after trimming).
countryNoOptional ISO-2 search country; omit for the default region.

Output Schema

NameRequiredDescriptionDefault
dataYes
statsNo
_debugNo
summaryYes
warningsNo
nextActionsYes
correlationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / pattern
      Previous value: -"[^\\t\\n\\v\\f\\r\\x85\\p{Z}]"New value: +"[^\\t\\n\\v\\f\\r\\x85    - 

   ]"
  2. Changed3 schema fields changed
    • addedOutput schema / properties / data / properties / context / anyOf
      Added value: +[
      +  {
      +    "type": [
      +      "null",
      +      "boolean",
      +      "number",
      +      "string",
      +      "array",
      +      "object"
      +    ]
      +  },
      +  {
      +    "additionalProperties": true,
      +    "properties": {
      +      "referenced": {
      +        "type": "boolean"
      +      },
      +      "rowCount": {
      +        "type": "integer"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "referenced",
      +      "rowCount",
      +      "url"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties / data / properties / context / type
      Removed value: -[
      -  "null",
      -  "boolean",
      -  "number",
      -  "string",
      -  "array",
      -  "object"
      -]
    • changedOutput schema / properties / data / properties / items / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "$ref": "#/$defs/value0"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "$ref": "#/$defs/value0"
      +        },
      +        {
      +          "additionalProperties": false,
      +          "properties": {
      +            "exportUrl": {
      +              "type": "string"
      +            },
      +            "payloadBytes": {
      +              "type": "integer"
      +            },
      +            "rowCount": {
      +              "type": "integer"
      +            },
      +            "token": {
      +              "type": "string"
      +            },
      +            "url": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "exportUrl",
      +            "payloadBytes",
      +            "rowCount",
      +            "token",
      +            "url"
      +          ],
      +          "type": "object"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, non-idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a hard cap of 10 results and relevance ordering, both of which affect how an agent should interpret and retry calls. It stops short of freshness, caching, rate limits, or cost, which matters for an open-world search.

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 sentence with zero wasted words, and the most decision-relevant fact (result count cap and ordering) is front-loaded. Nothing is buried or repeated from the title.

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?

An output schema exists, so return shape need not be explained, and both parameters are fully documented in the schema. What is missing is the routing information an agent actually needs in a catalog full of other search tools: when this web search is the right call versus the domain-specific searches.

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% — the query length bound and the optional ISO-2 country with its default are fully documented in the schema. The description adds no meaning beyond that (no query syntax, no examples, no interaction between query and country), so the baseline 3 applies.

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 identifies the resource precisely: 'public page titles, URLs and snippets' clearly marks this as open-web search rather than the internal data searches among its siblings (shipments, companies, hscode). The verb is implicit in 'Returns ... in relevance order' rather than stated as 'searches the web', which is the only thing keeping it from a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance at all — nothing tells the agent to prefer this over exim__hscode__search, exim__search__run, or any other sibling search tool. The reader must infer the selection rule entirely from the word 'public'.

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.