Skip to main content
Glama

Free web search

search_free
Read-onlyIdempotent

Search the web and return ranked result metadata (URL, title, snippet, date) for AI agents; read individual pages separately with fetch when full text is needed.

Instructions

Search the web and return ranked results: url, title, snippet, rank, provider, and published_at/modified_at when the engine gives a date. No page text; read a result with fetch. An identical search within 60 s returns cache_hit: true for 0 credits. Fields: https://clawifi.dev/docs/search

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

Input Schema

NameRequiredDescriptionDefault
queryYes
dry_runNoNot supported here: leave it out and use the estimate tool to price a call.
optionsNoOther API fields for this operation, merged into the request body as they are (see the Clawifi API docs).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "default": null,
      +  "description": "Not supported here: leave it out and use the estimate tool to price a call.",
      +  "title": "Dry Run"
      +}
    • addedInput schema / properties / options
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Other API fields for this operation, merged into the request body as they are (see the Clawifi API docs).",
      +  "title": "Options"
      +}
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered; the description adds genuinely new behavior: 60-second result caching with `cache_hit: true` at 0 credits, and the fact that date fields appear only when the engine supplies them. That is real credit/caching semantics the annotations cannot express. Minor gap: no mention of rate limits or result-count limits.

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?

Front-loaded with the action and return shape, then constraints, then a docs pointer — no filler sentences and every clause carries information. The trailing "Fields: https://clawifi.dev/docs/search" is terse to the point of being cryptic about what the link contains, which keeps it from a 5.

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?

Output schema exists, yet the description still helpfully sketches the result shape and the one non-obvious return flag (cache_hit). For a one-required-param read-only search it covers what an agent needs to call it correctly; only the opaque `options` parameter is left unexplained.

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 67% and the description mostly restates the schema's own dry_run guidance ("Not supported here: leave it out and use the estimate tool"). It adds a little meaning to `query` via the 60-second identical-search caching rule, but says nothing about the free-form `options` object, which is the least self-explanatory parameter. Baseline 3 fits given the schema does most of the work.

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?

Specific verb and resource ("Search the web") plus an enumeration of the returned fields (url, title, snippet, rank, provider, dates), and it explicitly separates itself from the sibling `fetch` with "No page text; read a result with fetch." An agent can distinguish this from the other retrieval tools without opening 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 clear routing: use `fetch` to read a result's page text, omit `dry_run` and use the estimate tool to price a call. It also sets the caching expectation (identical search within 60 s is free). It stops short of explicit when-not-to-use guidance relative to crawl/scrape/extract, but the sibling split it does give is concrete.

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