Skip to main content
Glama

Get X ranking weights

get_x_algorithm
Read-onlyIdempotent

Show the weight X's published ranking code gives each action it predicts a viewer will take on a post (reply, like, repost, report and the rest), when each weight last changed and from what, and the latest changes to the switches around them, such as the boost for new and small accounts. Read from X's public repository and refreshed about every hour. A weight multiplies a predicted probability, never a count of likes or replies, and how_to_read says what follows from that. For planning what and how to post on X.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourceYes
changesYesthe latest releases that changed a weight or a switch, newest first
checkedNowhen X's repository was last checked for newer values
weightsYes
publishedYeswhen X published the code these values are from
how_to_readYes
earlier_changesNohow many older releases are not listed
production_syncNowhen the file says its values were copied from production

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / changes / items / properties / changes / items / properties / status
      Added value: +{
      +  "description": "off: added at a value that does nothing yet, such as a flag at false, an empty list or a weight at 0. turned on, turned off: this change started or stopped it. It tells what the value did, not that a feature runs: a switch can wait on another that is still off. Absent where the value alone cannot say",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already state read-only, idempotent, non-destructive behavior. The description adds substantial context beyond that: the data source is X's public repository, it refreshes about hourly, weights multiply predicted probabilities rather than counts, and the tool includes change history for weights and related switches.

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?

The description is front-loaded and free of filler, but the first sentence is dense with several clauses about weights, change history, and switches. It remains readable, though splitting that content could improve scanability.

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?

For a zero-parameter read tool with an output schema and strong annotations, the description covers provenance, refresh cadence, weight semantics, change history, and intended use. Nothing essential for correct invocation appears to be missing.

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?

The tool takes no parameters, so the baseline is 4. The description does not need to explain parameter meaning, and no parameter semantics are missing.

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 states a specific verb and resource: it shows the weights X's published ranking code assigns to predicted viewer actions, plus weight change history and related switch changes. It enumerates the returned content and clearly distinguishes this from generic posting or context tools.

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?

It gives a clear usage context: 'For planning what and how to post on X.' It does not explicitly name when not to use it or point to alternatives, but there is no obvious overlapping sibling tool in the provided list.

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