Skip to main content
Glama

ProLevelMax

by com.prolevelmax
OverviewDiscussionsAdmin

Find a data source

procli_discover
Read-onlyIdempotent

Find data sources for a request in plain words, in English or Chinese (e.g. "tiktok comments", "小红书 评论", "微博热搜"). Returns ranked sources with what each is best for, its price, estimate.per100Results (about how much 100 results cost) and a verdict (recommended / ok / not_recommended) with the reason. Start from the recommended ones. Sources the user starred in the console come first (favorite: true) and are listed in favorites; prefer them when they fit. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many sources to return
queryYesWhat data you need, e.g. "reddit comments" or "抖音 热榜"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoExtra advice for this request
guideNoHow to use the list
itemsYesAll matching sources, best first
queryYesThe request as given
favoritesNoSources the user starred
recommendedNoShort list of the best sources for the request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "favorites": {
+      "description": "Sources the user starred",
+      "items": {
+        "properties": {
+          "platform": {
+            "description": "Platform",
+            "type": "string"
+          },
+          "scraper": {
+            "description": "Source id",
+            "type": "string"
+          },
+          "title": {
+            "description": "Source name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "guide": {
+      "description": "How to use the list",
+      "type": "string"
+    },
+    "items": {
+      "description": "All matching sources, best first",
+      "items": {
+        "properties": {
+          "bestFor": {
+            "description": "What it is best for",
+            "type": "string"
+          },
+          "description": {
+            "description": "What it returns",
+            "type": "string"
+          },
+          "estimate": {
+            "description": "Typical cost, e.g. per100Results",
+            "type": "object"
+          },
+          "favorite": {
+            "description": "true when the user starred it",
+            "type": "boolean"
+          },
+          "platform": {
+            "description": "Platform, e.g. tiktok, reddit, xiaohongshu",
+            "type": "string"
+          },
+          "pricing": {
+            "description": "Price of the source",
+            "properties": {
+              "amount": {
+                "description": "Price in USD per call or per result",
+                "type": "number"
+              },
+              "currency": {
+                "description": "Always USD",
+                "type": "string"
+              },
+              "display": {
+                "description": "Price as text, e.g. \"$0.003 per call\"",
+                "type": "string"
+              },
+              "type": {
+                "description": "PER_CALL (one page per call) or PER_RESULT (charged per row returned)",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "scraper": {
+            "description": "Source id",
+            "type": "string"
+          },
+          "title": {
+            "description": "Source name",
+            "type": "string"
+          },
+          "verdict": {
+            "description": "recommended, ok or not_recommended",
+            "type": "string"
+          },
+          "why": {
+            "description": "Reason for the verdict",
+            "type": "string"
+          }
+        },
+        "required": [
+          "scraper"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "description": "Extra advice for this request",
+      "type": "string"
+    },
+    "query": {
+      "description": "The request as given",
+      "type": "string"
+    },
+    "recommended": {
+      "description": "Short list of the best sources for the request",
+      "items": {
+        "properties": {
+          "per100Results": {
+            "description": "About what 100 results cost, in USD",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "price": {
+            "description": "Price as text",
+            "type": "string"
+          },
+          "scraper": {
+            "description": "Source id to pass to procli_inspect / procli_run",
+            "type": "string"
+          },
+          "title": {
+            "description": "Source name",
+            "type": "string"
+          },
+          "why": {
+            "description": "Why it is recommended",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "items"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/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, non-destructive, closed-world), and the description adds genuinely new context beyond them: the operation is 'Free', starred sources are surfaced first with a favorite flag, and the ranking/verdict semantics. It does not mention pagination or limits on repeated calls, but the read-only cost picture is well covered.

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-loads the core action and its input format in the first clause, then layers return shape and selection advice. Dense but every sentence carries information; the return-field enumeration is slightly long given an output schema exists.

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?

For a two-parameter, read-only discovery tool with a full schema and an output schema, the description supplies enough: input language flexibility, ranking/verdict meaning, favorites precedence, and zero cost. Minor omission is any hint about how this tool chains into procli_run, but nothing needed to invoke it correctly 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?

Schema description coverage is 100%, so both query and limit are already documented in the schema, including the inline examples 'reddit comments' and '抖音 热榜'. The description reinforces the query's free-form multi-language nature but adds no syntax or constraint detail beyond the schema, matching the baseline 3.

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?

Uses a concrete verb (Find) and resource (data sources) and states the accepted input form (plain words, English or Chinese, with inline examples). It is clearly the discovery entry point, cleanly distinct from sibling execution tools like procli_run and procli_inspect.

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?

Gives practical selection guidance for results — 'Start from the recommended ones' and 'prefer [favorites] when they fit' — and implicitly frames this as the first step before running a source. It never explicitly names a sibling tool or states when not to use it, so it stops short of full alternative routing.

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

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