SigRank — AI Operator Benchmarking

Get Leaderboard — Public Operator Rankings

get_leaderboard

Read-onlyIdempotent

Read the current public SigRank operator leaderboard. Returns ranked operators with Yield, Leverage, class tier, and display name.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of operators to return (1–100, default 25).
`window`	No	Time window for the leaderboard: 7d, 30d, 90d, or all_time.	30d
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."

Output Schema

TableJSON Schema

Name	Required	Description
`window`	No	The time window used for the query.
`entries`	No
`total_operators`	No	Number of operators returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 3, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "context"
+]
```

First observedSep 1, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds 'public' and 'current' as behavioral context, but it does not disclose pagination, rate-limit, or data-freshness behavior beyond that.

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: the first identifies the operation and object, and the second enumerates the returned fields. Every sentence earns its place, with no filler or repetition of schema details.

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?

Given rich annotations, full schema coverage, and an output schema, the description provides enough to invoke the tool correctly: what it reads and what it returns. It falls short only in signaling when to prefer this tool over its numerous siblings, which is a usage-guidance gap rather than a call-correctness gap.

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 the parameters (limit, window, context) are already well documented. The tool description adds no parameter-level semantics; the listed return fields concern output, not parameters, which is acceptable at the schema-covered baseline.

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?

The description starts with a concrete verb and resource: 'Read the current public SigRank operator leaderboard,' and it lists key return fields (Yield, Leverage, class tier, display name). It stops short of an explicit sibling contrast, so differentiation from tools like get_operator or rank_windows is implied by the term 'leaderboard' rather than stated.

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

Usage Guidelines2/5

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

The description gives no guidance on when to call this tool versus the many sibling tools, nor does it mention any exclusions or prerequisites. An agent must infer from the tool name and title that a leaderboard query is intended, which is thin guidance.

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

All SigRank — AI Operator Benchmarking tools Inspect

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.