Skip to main content
Glama
Sign In

ProLevelMax

by com.prolevelmax
OverviewDiscussionsAdmin
This connector has been deprecated

Duplicate listing. Use com.prolevelmax/prolevelmax: https://glama.ai/mcp/connectors/com.prolevelmax/prolevelmax

Find a data source

procli_discover
Read-onlyIdempotent

Searches the ProLevelMax catalog of data sources for a request written in plain words (e.g. "reddit comments", "amazon reviews", "tiktok comments"). Returns ranked sources, each with what it is best for, its price, estimate.per100Results (approximate cost of 100 results) and a verdict (recommended / ok / not_recommended) with the reason. Sources the user starred in the console are marked favorite: true and also listed under favorites. Free.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many sources to return
queryYesThe data needed, in plain words, e.g. "reddit comments" or "amazon reviews"

Output 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. Changed3 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"What data you need, e.g. \"reddit comments\" or \"抖音 热榜\""New value: +"The data needed, in plain words, e.g. \"reddit comments\" or \"amazon reviews\""
    • changedOutput schema / properties / items / items / properties / platform / description
      Previous value: -"Platform, e.g. tiktok, reddit, xiaohongshu"New value: +"Platform, e.g. reddit, tiktok, amazon"
    • changedOutput schema / properties / recommended / items / properties / scraper / description
      Previous value: -"Source id to pass to procli_inspect / procli_run"New value: +"Source id"
  2. 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"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real value by disclosing that results are ranked, carry a verdict with reasoning, and reflect console-starred favorites (marked favorite: true and duplicated under favorites). It also states the call is free. Remaining gaps are minor: no note on how limit interacts with ranking or on latency.

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?

A single front-loaded paragraph that opens with the action, then the return shape, then the free/favorites behavior — every clause carries information. It is slightly dense, and enumerating return fields overlaps with the existing output schema, but nothing is wasted.

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 rich annotations, full schema coverage and an output schema, the description covers what the tool does and what comes back, so an agent can invoke it correctly. The one missing piece is workflow placement relative to procli_run and procli_inspect, which matters in a seven-tool server.

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 parameters are already documented in the schema, including the 1–50 bound on limit. The description reinforces query semantics with plain-words phrasing and examples but adds nothing about limit's effect on ranking or truncation; baseline 3 is appropriate when the schema does the heavy lifting.

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 — "Searches the ProLevelMax catalog of data sources" — and immediately grounds it with plain-language query examples ("reddit comments", "amazon reviews"). An agent can tell this is a discovery/search tool rather than a run/inspect tool, though no sibling is named explicitly, so it falls just short of full sibling differentiation.

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 implied rather than stated: the agent can infer this is the entry point before calling procli_run, but the description never says "use this first to find a source ID" or names an alternative like procli_inspect. The only explicit usage-adjacent signal is "Free", which hints at a cost consideration but doesn't route the agent.

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