Skip to main content
Glama

HyperXosist-Agent Remote MCP

by io.github.KG-NINJA
OverviewDiscussionsAdmin

hyperxosist_search_plan

Read-onlyIdempotent

Use only for specialized X (Twitter) research planning: complaints, bug reports, feature requests, product feedback, or community signals. Builds multiple noise-reduced official x.com/search URLs and quality scores. It is not general web search and does not scrape X or collect posts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYesAn X-specific research goal, for example: Find user complaints and bug reports on X about Acme.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
missionYes
queriesYes
missionIdYes
searchUrlsYes
paymentPolicyYes
qualityScoresYes
estimatedCostUsdYes
requiresPaymentForAutomatedProductionUseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedOutput schema / properties / accessTier
      Removed value: -{
-  "const": "free"
-}
    • removedOutput schema / properties / canonicalOpenApi
      Removed value: -{
-  "format": "uri",
-  "type": "string"
-}
    • removedOutput schema / properties / paidEndpoint
      Removed value: -{
-  "format": "uri",
-  "type": "string"
-}
    • removedOutput schema / properties / upgradeNotRequiredWhen
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedOutput schema / properties / upgradeRequiredWhen
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • changedOutput schema / required
      Previous value: -[
-  "type",
-  "missionId",
-  "mission",
-  "queries",
-  "searchUrls",
-  "qualityScores",
-  "estimatedCostUsd",
-  "requiresPaymentForAutomatedProductionUse",
-  "paymentPolicy",
-  "accessTier",
-  "canonicalOpenApi",
-  "paidEndpoint",
-  "upgradeRequiredWhen",
-  "upgradeNotRequiredWhen"
-]New value: +[
+  "type",
+  "missionId",
+  "mission",
+  "queries",
+  "searchUrls",
+  "qualityScores",
+  "estimatedCostUsd",
+  "requiresPaymentForAutomatedProductionUse",
+  "paymentPolicy"
+]
  2. Changed6 schema fields changed
    • addedOutput schema / properties / accessTier
      Added value: +{
+  "const": "free"
+}
    • addedOutput schema / properties / canonicalOpenApi
      Added value: +{
+  "format": "uri",
+  "type": "string"
+}
    • addedOutput schema / properties / paidEndpoint
      Added value: +{
+  "format": "uri",
+  "type": "string"
+}
    • addedOutput schema / properties / upgradeNotRequiredWhen
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / upgradeRequiredWhen
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "type",
-  "missionId",
-  "mission",
-  "queries",
-  "searchUrls",
-  "qualityScores",
-  "estimatedCostUsd",
-  "requiresPaymentForAutomatedProductionUse",
-  "paymentPolicy"
-]New value: +[
+  "type",
+  "missionId",
+  "mission",
+  "queries",
+  "searchUrls",
+  "qualityScores",
+  "estimatedCostUsd",
+  "requiresPaymentForAutomatedProductionUse",
+  "paymentPolicy",
+  "accessTier",
+  "canonicalOpenApi",
+  "paidEndpoint",
+  "upgradeRequiredWhen",
+  "upgradeNotRequiredWhen"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds that it builds noise-reduced URLs and quality scores, and does not scrape or collect posts. This is useful but modest; no mention of response format or authorization, which output schema partially covers.

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 sentences, each earning its place. First sentence states purpose and usage scope; second sentence clarifies exclusions. No redundancy or unnecessary detail.

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?

With only one parameter, high schema coverage, and an output schema, the description is fully adequate. It covers purpose, usage boundaries, and behavioral constraints. No missing information for a tool of this complexity.

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?

The single parameter 'intent' is fully described in the schema with an example. Description enriches by listing specific intent categories (complaints, bug reports, etc.), adding meaning beyond the schema's generic 'research goal'.

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?

Clearly states it's for specialized X (Twitter) research planning, lists specific use cases (complaints, bug reports, etc.), and distinguishes from general web search and scraping. The verb 'search_plan' combined with 'builds URLs and quality scores' defines a specific resource and action.

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

Usage Guidelines4/5

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

Explicitly limits usage to X research planning and provides examples of when to use. Also clarifies what it is not (not general web search, not scraping). However, it does not explicitly compare to sibling tools (build_handoff, filter_signals), which could help further.

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

All HyperXosist-Agent Remote MCP 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