Skip to main content
Glama

Search the Web

search
Read-only

Find web results for a query using TinyFish, optionally falling back to keyless Firecrawl, with controls for provider, result limit, domains, language, and location.

Instructions

Search with TinyFish, optionally falling back once to keyless Firecrawl Search. TinyFish requires a free-only confirmed API key.

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
limitNo
queryYes
optionsNo
fallbackNo
providerNoauto

Output Schema

NameRequiredDescriptionDefault
queryYes
partialYes
resultsYes
attemptsYes
providerYes
warningsYes
requestedProviderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavior — a single fallback attempt and an authentication requirement (free-only confirmed API key) that materially affects whether a call succeeds. It does not disclose rate limits, quota behavior, or what happens when both providers fail, 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?

Two short sentences with no filler, but the opening clause is spent on provider mechanics rather than front-loading what the tool actually returns or searches. Efficient, though the framing prioritizes implementation detail over the agent's decision.

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?

With an output schema present, return values need not be explained, and the auth/fallback story is covered. However, for a 5-parameter tool with a nested options object and zero schema description coverage, leaving pagination, language/location, and domain filtering unexplained is a real gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters including a nested options object (page, language, location, include/excludeDomains), and the description explains none of them. The only partial coverage is incidental: 'falling back once' hints at the fallback boolean and the provider names match the enum values, but limit, options, and pagination semantics are left entirely undocumented.

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 names a concrete verb ('Search') and the two backing providers (TinyFish, Firecrawl Search), so an agent knows this is a web-search tool rather than a fetch/browse/crawl operation. It stops short of explicitly contrasting itself with the sibling browse/fetch tools, so it lands at 4 rather than 5.

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?

It gives provider-selection context ('optionally falling back once to keyless Firecrawl Search') and a prerequisite for the primary provider ('TinyFish requires a free-only confirmed API key'), which implies when it will work. It never states when to choose search over browse/fetch or when search is inappropriate, so guidance is only implied.

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