Skip to main content
Glama

Search the web

stork_search
Read-only

Search the web for a query and return ranked results with titles, addresses, and text snippets, using a named third-party search provider.

Instructions

Search the web. Returns ranked results with titles, addresses and text snippets for a query. The search is run by a web search provider (Exa today), which is named in the reply's via field. Results are third-party content.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results. Default 5.
queryYesWhat to search for.
max_result_tokensNoCap on the size of the reply. Default 3000, at most 6000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the search is executed by a third-party provider (Exa today) whose name appears in the reply's `via` field, and results are explicitly flagged as third-party content — a trust/provenance caveat the agent would not otherwise have. Rate limits and pagination are not mentioned.

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?

Three short sentences, front-loaded with the core action and followed by return shape and provenance. No filler, though the opening sentence duplicates the title verbatim and could have been merged with the second.

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 no output schema, the description usefully characterizes the return value (ranked results with titles, addresses, snippets) and the provenance field, which is exactly what an agent needs. The remaining gap is guidance on search-versus-scrape selection, which is the one thing missing for correct tool choice.

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 coverage is 100%, so the schema already documents all three parameters including defaults and the 1–10 and 6000 limits. The description adds no further meaning about `limit` or `max_result_tokens`; its only field-level mention (`via`) concerns the response, not an input. 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 gives a specific verb and resource ("Search the web") and spells out the shape of what comes back: ranked results with titles, addresses and text snippets. It is clear on its own, but it never contrasts itself with the sibling `stork_scrape`, which is the closest alternative for fetching web content.

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 statement of when to use this tool versus `stork_scrape` or `stork_docs`, and no preconditions or exclusions. Usage can only be inferred from the generic phrase "Search the web", leaving the agent to guess between search and scrape on its own.

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