Skip to main content
Glama

get_outliers

Identify papers without an S3 link above a chosen similarity threshold, ranked by citation count, with nearest similarity scores and suggested communities.

Instructions

Papers with no S3 link above the chosen threshold (the "irrelevant" set), most cited first, with their nearest similarity and suggested community.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_outliers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
run_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the result ordering (most cited first) and the returned fields (nearest similarity, suggested community), which is real added value. It never states that this is a non-mutating read, nor how limit/pagination behaves, so the behavioral picture is incomplete.

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?

A single compact sentence that front-loads the defining filter and then the ordering and payload. Nothing is redundant, though the dangling "chosen threshold" reference is a small clarity cost.

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

Completeness3/5

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

The output schema removes the need to explain return values, and the tool is low-complexity with one required parameter. Still, the unexplained threshold-versus-run_id relationship and the silent limit parameter leave an agent guessing at how scope is actually determined.

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

Parameters2/5

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

Schema description coverage is 0% across two parameters, so the description must compensate and does not: run_id and limit are never mentioned. Worse, it refers to "the chosen threshold", a concept with no corresponding parameter in the schema, which could lead an agent to hunt for a threshold argument that does not exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description defines the exact resource: papers with no S3 link above a threshold, i.e. the "irrelevant" set, sorted most-cited-first. That is specific enough to distinguish it from list-style siblings. It stops short of 5 because the action verb is only implied by the name and there is no explicit differentiation from get_threshold_scan, which sounds adjacent.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for surfacing low-relevance/most-cited outliers in a run. There is no explicit when-to-use, no when-not-to-use, and no named alternative for the related threshold-scan or citation-structure queries.

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