Skip to main content
Glama

SOTA2 — AI Solution Rankings

Get AI solution rankings

get_solution_rankings
Read-onlyIdempotent

Compares AI software for a known industry/task using published positions, reasons, best use cases, evidence and caveats. Use a scope from find_ai_solutions or industry/task discovery, including follow-ups such as why a product ranks first or the next page. Industry only returns a task directory; industry + task selects that exact scope; task only selects cross-industry. Missing combinations return not_found with guidance, never substitute rankings. Positions/scores are scoped, not comparable across scopes; unreviewed positions/scores are null. Top N corresponds to limit N rows.

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_solution_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNo
limitNoRequested number of individual result rows (1–50): top 2 corresponds to limit 2. Also the page size for continuation requests.
offsetNoRow offset. Use nextOffset from the previous response.
industryNo

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior the annotations do not: no silent substitution on missing scopes, null positions/scores for unreviewed items, and scoped rather than cross-comparable rankings. Return shape itself is left to the output schema, which is appropriate.

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?

Purpose and prerequisite lead, followed by scope rules, failure behavior, and comparability caveats — a sensible front-loaded order with essentially no filler. The middle sentences are dense with semicolon-chained rules, which slightly hurts scanability but nothing is redundant.

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 an output schema present, the description need not explain the payload, and it covers the remaining agent-critical facts: scope resolution, not_found behavior, pagination via nextOffset, and ranking comparability. A hint about what the industry-only task directory looks like would close the last gap.

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 coverage is 50% — limit and offset are documented in-schema, while industry and task have no descriptions. The description compensates by defining exactly what each scope combination selects, and restates the limit-to-N mapping. Offset paging is only implied via 'next page' rather than explained.

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?

States a specific verb and resource ('Compares AI software') plus the scope it operates on (industry/task) and what the payload contains (positions, reasons, use cases, evidence, caveats). It also implicitly separates itself from find_ai_solutions by requiring a scope that discover tool produced.

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 names the prerequisite source ('Use a scope from find_ai_solutions or industry/task discovery') and the follow-up patterns it serves (why a product ranks first, next page). It also spells out the scope-selection matrix — industry only, industry + task, task only — and states that missing combinations return not_found with guidance rather than substituting rankings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources