Skip to main content
Glama
Sign In

Scrappa

by co.scrappa
OverviewDiscussionsAdmin

Search the web with Google

google_search
Read-onlyIdempotent

Search Google and get the organic web results for a query. Returns per result: position, title, link and snippet. Use it for current information from the web. Reads public data only.

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

Input Schema

NameRequiredDescriptionDefault
numNoNumber of results, 1 to 10. Default: 10.
queryYesThe search query, e.g. "best coffee grinder 2026".
countryNoTwo-letter country code for local results, e.g. "us" or "de". Default: us.
languageNoTwo-letter language code, e.g. "en" or "de". Default: en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond them by enumerating the return shape (position, title, link, snippet) and confirming public-data-only access with no personal or authenticated scope. Pagination and rate-limit behavior remain undisclosed.

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?

Three short sentences, each earning its place: purpose first, return shape second, usage and access scope third. No filler and the core verb leads.

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 compensates by listing the returned fields, and rich annotations cover the safety and open-world behavior. Only minor gaps remain, such as result-set size limits or pagination behavior, which are partly implied by the num parameter.

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% with all four parameters documented including defaults and examples, so the schema carries parameter semantics fully. The description adds no meaning beyond the schema, which is the baseline-3 case.

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?

States a specific verb (Search) and resource (Google organic web results) plus the returned fields, which cleanly separates it from the maps, flights, Trustpilot and YouTube siblings. It never names a sibling explicitly, so differentiation comes from the resource wording rather than deliberate routing.

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?

"Use it for current information from the web" gives a broad usage context but no when-not conditions and no named alternative among the five sibling tools. An agent can infer the vertical split from the tool names, but the description does no active work here.

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

All Scrappa toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources