Skip to main content
Glama

get_operator

Read-only

Fetch a specific operator's live profile from the SigRank board using their public codename. Returns detailed metrics including yield, leverage ratio, class tier, rank, and per-window breakdowns for 7d, 30d, 90d, and all-time.

Instructions

Fetches one operator's live profile from the SigRank board by their codename. Reads the operator's current submission data from signalaf.com and returns their detailed metrics: yield (Υ), leverage ratio (Cr/I), velocity (O/I), class tier (Burner / Builder / 10xer), rank position (integer, 1-based), and per-window breakdowns for each time range (7d, 30d, 90d, all-time) with the four canonical pillars (input, output, cacheCreate, cacheRead) per window. Returns an error if the codename is not found on the board. Use this to look up any operator who has submitted to the board — codenames are public and visible on the leaderboard. Do NOT use this to browse all operators — use get_leaderboard for that. After calling this, you can use simulate_change to model what would happen if the operator adjusted their token mix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codenameYesThe operator's public codename as shown on the SigRank leaderboard. Case-insensitive — "Ghost Falcon" and "ghost falcon" are equivalent. Must match a codename that exists on the board; returns an error if not found. To discover valid codenames, call get_leaderboard first.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rankNo1-based rank position
classNo
yield_NoΥ Yield metric
windowsNoPer-window breakdowns (7d, 30d, 90d, all-time)
codenameNoOperator display name
leverageNoCr/I ratio
velocityNoO/I ratio
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description confirms it reads data without mutation. It adds details about returned fields, error behavior, and the public nature of codenames, surpassing annotation scope.

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?

Well-structured with immediate purpose, then specifics. However, it is somewhat verbose and includes some repetition (e.g., error condition mentioned twice). Every sentence adds value, but could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (detailed return metrics) and presence of an output schema, the description thoroughly covers all aspects: what it does, what it returns, error conditions, and how to use it with other tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. The description adds semantic value: case-insensitivity, requirement to match existing codename, error handling, and advice to call get_leaderboard first for valid codenames.

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 clearly states the tool fetches one operator's live profile by codename, listing the specific metrics returned. It distinguishes from sibling tools get_leaderboard (browse all) and simulate_change (model adjustments).

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

Usage Guidelines5/5

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

Explicitly states when to use (look up specific operator) and when not to (use get_leaderboard for browsing). Also suggests subsequent use of simulate_change.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SunrisesIllNeverSee/sigrank-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server