Skip to main content
Glama
Sign In

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Google AI Mode

ai_mode
Read-onlyIdempotent

Ask Google AI Mode and get its answer with cited sources and products. 2 credits; takes 5-45 s; free if it fails.

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": {
      "prompt": "<prompt>"
    },
    "name": "ai_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackNoBrands or domains to check the answer for (mentions: named in the text, cited, listed as a source or product)
promptYesThe message to the assistant (up to 4,000 characters)
countryNoAsk from this country, e.g. us, de, gb (answers, prices and shops follow it)
languageNoInterface language, e.g. en, de
locationNoCity-level location the answer is for, e.g. "Austin, Texas, United States"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / location
      Added value: +{
+  "description": "City-level location the answer is for, e.g. \"Austin, Texas, United States\"",
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Ask from this country, e.g. us, de, gb (answers, prices and shops follow it)",
+  "type": "string"
+}
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Interface language, e.g. en, de",
+  "type": "string"
+}
    • addedInput schema / properties / prompt
      Added value: +{
+  "description": "The message to the assistant (up to 4,000 characters)",
+  "type": "string"
+}
    • addedInput schema / properties / track
      Added value: +{
+  "description": "Brands or domains to check the answer for (mentions: named in the text, cited, listed as a source or product)",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing the billing cost (2 credits), the variable latency window (5-45 s), and the failure policy (free if it fails) — exactly the kind of risk/cost context an agent needs before committing. It does not describe the shape of the returned answer beyond sources and products, leaving that gap.

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?

A single tight sentence with the capability front-loaded and the operational facts (cost, duration, failure billing) packed into compact clauses. Nothing is wasted or redundant.

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 five fully documented parameters and no output schema, the description covers what is needed: what it returns (answer plus cited sources and products), cost, and timing. A brief note on result variability or how tracked brands surface would complete it, but nothing critical is missing.

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?

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the description only needs to add operational context, which it does with cost and latency. It adds nothing about the parameters themselves, relying entirely on the 100%-covered schema, which is the correct baseline.

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?

"Ask Google AI Mode and get its answer with cited sources and products" states a specific verb (ask) and resource (Google AI Mode), and the product name itself separates it from generic answer/chatgpt/gemini siblings. It stops short of explicitly contrasting itself with those alternatives, but the intent is unambiguous.

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?

There is no explicit when-to-use / when-not-to-use guidance or named alternative. Usage is only implied by the shared-economics note (2 credits, 5-45 s), which lets an agent weigh it against cheaper siblings like search or answer, but the agent must infer that tradeoff itself.

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

All SerpKite 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