platform.quality.rankings
Get ranked list of tools by quality — sort by uptime (most reliable), latency (fastest), or error_rate (fewest errors). Filter by category (e.g. "crypto", "weather"). Discover the best tools for your use case. Free, no charge (APIbase)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/platform.quality.rankings.md
What platform.quality.rankings does on Apibase
AI agents call platform.quality.rankings to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort | string | — | Sort by: "uptime" (highest availability), "latency" (fastest p50), or "error_rate" (lowest errors). Default: "uptime" |
limit | integer | — | Max number of tools to return (1-100). Default: 20 |
category | string | — | Filter by tool category prefix (e.g. "crypto", "weather", "finance") |
Parameters from the server's own tool schema.
Why platform.quality.rankings is rated Low
Retrieves quality metrics and rankings; read-only query with no side effects or data modification.
From the tool's definition Get ranked list of tools by quality — sort by uptime, latency, or error_rate.
Attacks that exploit this kind of access
The rule that runs platform.quality.rankings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For platform.quality.rankings, this is the rule to start with:
platform.quality.rankings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every platform.quality.rankings call is checked against it from then on.
Questions about platform.quality.rankings
Get ranked list of tools by quality — sort by uptime (most reliable), latency (fastest), or error_rate (fewest errors). Filter by category (e.g. "crypto", "weather"). Discover the best tools for your use case. Free, no charge (APIbase). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
platform.quality.rankings accepts 3 parameters: sort, limit, category. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for platform.quality.rankings: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Apibase. Nothing to install.
platform.quality.rankings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the platform.quality.rankings rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for platform.quality.rankings. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
platform.quality.rankings is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue