Skip to main content
Glama
O-mega-Enterprise

suprsonic-mcp

by O-mega-Enterprise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search

Query the web for raw Google SERP results, AI-synthesized answers with citations, or both combined to support research and fact-checking.

Instructions

Search the web with SERP, AI synthesis, or both. Cost: serp 1 credit, ai 2 credits, deep 3 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoMode: serp (Raw Google SERP results), ai (AI-synthesized answers with citations), deep (SERP + AI synthesis combined).
queryYesThe search query.
countryNoISO country code of the Google results (serp and deep modes).us
freshnessNoOnly sources from this window, in every mode.any
num_resultsNoMaximum number of organic results (serp and deep modes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.3.1
    • addedInput schema / properties / country
      Added value: +{
+  "default": "us",
+  "description": "ISO country code of the Google results (serp and deep modes).",
+  "type": "string"
+}
    • addedInput schema / properties / freshness
      Added value: +{
+  "default": "any",
+  "description": "Only sources from this window, in every mode.",
+  "enum": [
+    "any",
+    "day",
+    "week",
+    "month"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / mode / default
      Removed value: -"ai"
    • changedInput schema / properties / mode / description
      Previous value: -"ai (2 credits, synthesized answer), serp (1 credit, raw links), or deep (3 credits, both)"New value: +"Mode: serp (Raw Google SERP results), ai (AI-synthesized answers with citations), deep (SERP + AI synthesis combined)."
    • addedInput schema / properties / mode / enum
      Added value: +[
+  "serp",
+  "ai",
+  "deep"
+]
    • changedInput schema / properties / num_results / description
      Previous value: -"Max results for serp/deep mode"New value: +"Maximum number of organic results (serp and deep modes)."
    • changedInput schema / properties / query / description
      Previous value: -"Search query"New value: +"The search query."
  2. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses credit cost per mode, which is real added context, but says nothing about output format, latency, rate limits, or result structure for a tool whose return shape is undefined by any output schema.

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?

Two tight sentences with zero filler, and the mode enumeration is front-loaded ahead of the cost table. Every clause earns its place.

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?

For a 5-parameter search tool with fully documented schema but no output schema, the definition covers modes and pricing adequately. The notable gap is that, absent an output schema, it never describes what a result looks like or how many results/services are returned.

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%, so the schema already documents mode, query, country, freshness, and num_results thoroughly; baseline 3 applies. The cost mapping hints at mode tradeoffs, but the description adds no format or syntax detail beyond the schema.

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 and resource ('Search the web') and enumerates its three delivery modes (SERP, AI synthesis, or both). The purpose is unmistakable, but it offers no differentiation from adjacent siblings like research, site-intel, or scrape.

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?

The cost-per-mode breakdown (serp 1, ai 2, deep 3 credits) implicitly guides mode selection toward the cheapest sufficient option. However, there is no explicit when-to-use guidance, no exclusion of alternate tools (research, scrape, site-intel), and no statement of when each mode is appropriate.

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

Deploy Server

Other Tools