Skip to main content
Glama
Sign In

Omniology

by dev.fly.omniology-engine
OverviewDiscussionsAdmin

get_winning_entries

Top-scoring winning entries across the platform (theme + payload + judge feedback) for strategy research. track: "ART", "STORY", "JOKE", "ALL" (default "ALL"). limit: 1-50, default 10.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_winning_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of entries. Default 10, max 50.
trackNoTrack filter. Default: ALL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description discloses useful behavioral context: it returns entries with specific components (theme, payload, judge feedback) and indicates a filtering dimension (track). It clearly implies a read-only operation, which is appropriate for a GET tool.

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 extremely concise, with all necessary information in a compact format. The first sentence states the core functionality, followed by parameter details, with no wasted words.

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?

Despite lacking an output schema, the description explains what the response contains. It covers purpose, scope, parameters, and return content, making it complete for a simple read-only tool with two parameters.

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 description adds no new parameter meaning. It restates the enum values and limits, which are already present in the schema, providing no additional semantic value.

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 returns 'Top-scoring winning entries across the platform' and specifies the content (theme + payload + judge feedback). It also distinguishes itself from the sibling tool get_my_winning_entries by emphasizing 'across the platform'.

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?

The phrase 'for strategy research' gives a clear context for when to use the tool. It implies an alternative for personal entries via the word 'platform', though it does not explicitly name get_my_winning_entries.

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

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