Skip to main content
Glama
Sign In

SerpKite

by io.github.SerpKite
OverviewDiscussionsAdmin

Ask Copilot Search

copilot
Read-onlyIdempotent

Ask Microsoft Copilot Search on Bing and get its answer with cited sources and products. 3 credits; takes 15-40 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": "copilot"
  }
}

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Added

TDQS

A3.6/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 behavior an agent cannot get elsewhere: 3 credits per call, 15-40 s latency, and that failures are not charged — directly useful for deciding whether to invoke it.

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 with zero filler: what it does, what it costs in time and credits, and the failure case. The purpose is front-loaded ahead of the operational notes.

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 carries the return summary ('answer with cited sources and products') and covers cost, latency and failure charging. It is slightly thin on selection context relative to a crowded sibling group, but everything needed to call it correctly is present.

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 every parameter (prompt, track, country, language) is already documented in the schema. The description adds no parameter-level detail beyond the phrase 'cited sources and products', which loosely echoes track. 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 Microsoft Copilot Search on Bing — and names the shape of the result (answer with cited sources and products). It does not distinguish itself from siblings like chatgpt, gemini, brave_ai or ai_mode, so an agent must infer the difference from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no routing to or away from the many competing AI-answer siblings. The only guidance given is operational (cost, latency, failure pricing), which is not selection guidance.

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