Skip to main content
Glama
Sign In

AiSeek

by dev.aiseek
OverviewDiscussionsAdmin

Search changes

search_changes
Read-onlyIdempotent

Search published changes by words, ranked by relevance, best first, not by time. Use it to find changes about a company, country, subject or name; to browse what is newest use list_changes, for a curated subject use get_topic, for a company's profile use search_companies. Parameters: query is matched against headlines and summaries in the language of locale, so search in that language (a Chinese or Japanese query also matches simplified, traditional and Japanese forms of the same characters); limit trims the ranked list (1 to 25). Behavior: no match is an empty list, not an error; each result's id feeds get_change. One call of the key's quota (Free keys have a daily MCP cap); a rejected argument costs nothing.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many changes to return, 1 to 25, best match first; omit for the connection's default (10 unless set)
queryYesWords to look for, 2 to 120 characters: a company, a country, a subject or a name, in any of the three languages
localeNoLanguage of headlines, summaries and notices in the answer: en, zh or ja; omit for the connection's default language (en unless set)

Output Schema

NameRequiredDescriptionDefault
itemsYesMatching changes, most relevant first; at most `limit`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / limit / default
      Removed value: -10
    • changedInput schema / properties / limit / description
      Previous value: -"How many changes to return, 1 to 25 (default 10), best match first"New value: +"How many changes to return, 1 to 25, best match first; omit for the connection's default (10 unless set)"
    • removedInput schema / properties / locale / default
      Removed value: -"en"
    • changedInput schema / properties / locale / description
      Previous value: -"Language of headlines, summaries and notices in the answer: en (the default), zh or ja"New value: +"Language of headlines, summaries and notices in the answer: en, zh or ja; omit for the connection's default language (en unless set)"
    • changedOutput schema / properties / items / items / properties / id / description
      Previous value: -"The change id (a UUID): pass it to get_change or change_history"New value: +"The change id (a UUID): pass it to get_change or get_change_history"
  2. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many changes to return, 1 to 25 (default 10), best match first"
    • changedInput schema / properties / locale / description
      Previous value: -"Language of titles and summaries: en, zh or ja"New value: +"Language of headlines, summaries and notices in the answer: en (the default), zh or ja"
    • addedInput schema / properties / query / description
      Added value: +"Words to look for, 2 to 120 characters: a company, a country, a subject or a name, in any of the three languages"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "items": {
+      "description": "Matching changes, most relevant first; at most `limit`",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "detectedAt": {
+            "description": "ISO 8601 time AiSeek detected the change",
+            "type": "string"
+          },
+          "evidenceStrength": {
+            "description": "How strong the evidence is, from 0 to 1",
+            "type": "number"
+          },
+          "id": {
+            "description": "The change id (a UUID): pass it to get_change or change_history",
+            "type": "string"
+          },
+          "importanceScore": {
+            "description": "Importance from 0 to 1",
+            "type": "number"
+          },
+          "primaryEntity": {
+            "anyOf": [
+              {
+                "additionalProperties": {},
+                "properties": {
+                  "name": {
+                    "type": "string"
+                  },
+                  "slug": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "slug",
+                  "name"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The main company or subject of the change"
+          },
+          "reportedAt": {
+            "description": "ISO 8601 time the first source reported it, when known",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "signalType": {
+            "description": "The kind of change",
+            "type": "string"
+          },
+          "summary": {
+            "description": "One- or two-sentence summary in the requested language; null when there is none",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "description": "Headline in the requested language",
+            "type": "string"
+          },
+          "url": {
+            "description": "The change's page on aiseek.dev in the requested language",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "detectedAt",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), and the description adds genuinely useful context: empty list instead of an error on no match, result ids feeding get_change, and quota accounting including that a rejected argument costs nothing. It does not, however, describe the result shape or ordering guarantees beyond ranking, which is largely delegated to the 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then routing, then parameters, then behavior, with zero filler sentences. It is dense and long-ish, but each clause carries distinct information; only the quota sentence could arguably be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with a full output schema, the description covers everything an agent needs: selection criteria, ranked-vs-time semantics, language matching, limit bounds, no-match behavior, and follow-up linkage via id. No gaps remain that would cause a misinvocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: query is matched against headlines and summaries in the locale language and cross-matches simplified/traditional/Japanese character forms, and limit trims the ranked list. Those are non-obvious semantics the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (search published changes) plus the ranking rule (by relevance, best first, not by time), which immediately separates it from the chronological siblings. An agent can distinguish it from list_changes without opening any schema.

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

Usage Guidelines5/5

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

It names four concrete use cases and routes each alternative scenario to the right sibling: newest browsing to list_changes, curated subjects to get_topic, company profiles to search_companies. Everything needed to choose among alternatives is stated explicitly.

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

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