Skip to main content
Glama

SigRank — AI Operator Benchmarking

by com.signalaf
OverviewDiscussionsAdmin

Rank Windows — Multi-Window Cascade

rank_windows
Read-onlyIdempotent

Score up to 4 time windows (7d, 30d, 90d, all-time) in one call. Each window is scored independently with the full cascade (Υ, SNR, Leverage, Velocity, 10xDEV, class). Omit windows you don't have — partial input is allowed (1-4 windows). Does NOT submit to the board.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
7dNo7-day window token pillars (optional)
30dNo30-day window token pillars (optional)
90dNo90-day window token pillars (optional)
allNoAll-time window token pillars (optional)
contextYesExplain 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."

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, and the description adds genuinely useful behavioral context: each window is scored independently, the full cascade is applied, and no board submission occurs. This goes beyond the structured annotations without contradicting them.

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?

The description is four short, dense sentences, each contributing a distinct piece of information: multi-window scope, independent cascade scoring, partial-input allowance, and no board submission. It is front-loaded with the most important detail and contains no filler.

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 schema and annotations covering parameter shapes and safety, the description supplies the remaining operational context: window names, cascade stages, partial-input rule, and the absence of submission. A minor gap is that no output schema exists and the description does not explicitly state the return shape, though the cascade list strongly implies the scored result.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by clarifying that windows can be omitted, partial input of 1-4 windows is allowed, and each window is scored independently. This helps an agent understand optional-window behavior beyond what the schema's 'optional' flags convey.

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?

The description opens with a specific verb and resource: 'Score up to 4 time windows (7d, 30d, 90d, all-time) in one call.' It also names the exact cascade stages and explicitly states 'Does NOT submit to the board,' which differentiates this tool from sibling ranking/submission tools.

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?

It clearly tells the agent when to use the tool: for multi-window scoring, with partial input allowed (1-4 windows) and omitted windows permitted. The 'Does NOT submit to the board' line provides an exclusion, but the description does not name a specific alternative sibling or fully explain when to prefer rank_if or rank_paste.

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