Skip to main content
Glama
Sign In

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Ask Brave

brave_ai
Read-onlyIdempotent

Ask Brave Search's AI answer and get it with cited sources, the searches it ran and products. 2 credits; takes 1-10 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": "brave_ai"
  }
}

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?

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely non-obvious behavior: a 2-credit cost, 1-10 s latency, and no charge on failure. That failure-billing detail is exactly the kind of operational fact an agent cannot get from structured fields. It stops short of permissions or rate-limit context, but the value added is real.

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 short sentences with zero filler: the first defines the operation and its return, the second front-loads cost and latency. Nothing repeats the title or the schema.

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 enumerates what comes back (sources, executed searches, products), and it covers cost and timing, which are the main risks for an open-world call. The remaining gap is routing guidance against the crowded family of answer/search siblings, which matters given 21 alternatives.

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% and each of the five parameters carries a clear field description (including what 'track' means for brand mentions), so the burden is already met by the schema. The description adds no parameter-level meaning such as prompt phrasing advice or how country/location interact, so baseline 3 applies.

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 ('Ask Brave Search's AI answer') and describes the payload ('cited sources, the searches it ran and products'), so an agent knows this returns a synthesized answer with citations rather than raw results. It does not distinguish itself from the many answer-like siblings (answer, ai_mode, chatgpt, gemini, research), so a reader still has to guess why this one over those.

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?

Usage is only implied: the word 'Ask' plus a 'prompt' parameter suggests question-answering, and the credit/latency note hints this is a heavier call than a plain search. There is no explicit when-to-use, when-not-to-use, or named alternative among the 22 siblings.

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