Skip to main content
Glama

lane_leaders

State of the art of a topic BY GRAPH TRAVERSAL: for every benchmark lane (dataset × metric × experimental protocol) in the topic's expert graph, the paper at the top of the better chain — the one that beats others and is beaten by none — with the edge evidence (values compared). Use for 'what is SOTA on ' when you want the answer as graph structure; sota_papers gives fuller rows. [Free · 3 credits]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic_id": "<topic_id>"
    },
    "name": "lane_leaders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
topic_idYesTopic UUID (see list_experts / topic_overview)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 carries the burden and does well: it discloses the traversal semantics ('better' chain, beats others / beaten by none), that edge evidence with compared values is included, and the credit cost. It does not say what happens for topics with no comparable lanes or how the per-lane result set is bounded, so it stops short of full behavioral disclosure.

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?

Front-loads the core definition and the disambiguating usage sentence, with the credit tag kept short at the end. The parenthetical 'the one that beats others and is beaten by none' is somewhat redundant with the preceding 'top of the better chain', but overall it earns its length.

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?

No output schema exists, and the description compensates by describing the returned structure (lanes, top paper, edge evidence with values). For a 2-parameter read tool with no annotations, the main remaining gap is limit semantics and edge-case behavior when a lane has no dominating paper.

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 coverage is 50%: topic_id is documented in the schema, while limit only has type/default/min/max with no description. The description's talk of 'every benchmark lane' implies limit caps lanes, but it never says so explicitly, so the schema does most of the work with only marginal added meaning.

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?

Names a concrete verb and resource ('State of the art of a topic BY GRAPH TRAVERSAL') and explains the exact unit returned: the top paper per benchmark lane (dataset × metric × protocol) with edge evidence. It explicitly distinguishes itself from the sibling sota_papers, so an agent can pick between them without opening a schema.

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?

States the triggering question verbatim ('what is SOTA on <topic>') and the condition that selects this tool ('when you want the answer as graph structure'), then names the alternative and what it gives instead ('sota_papers gives fuller rows'). When-to-use and alternative routing are both explicit.

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