Skip to main content
Glama
mcp-server-everesteer

mcp-server-everesteer

Scoring rules & payout formula

explain_scoring
Read-onlyIdempotent

Returns the live payout formula, score multiple constant b, and FIT/UNQ/INOV rules so you can self-score offline without hardcoding b.

Instructions

Return the live payout formula, score_multiple_constant b, and FIT/UNQ/INOV rules.

Read weights.score_multiple_constant here before self-scoring offline; never hardcode b.

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": "explain_scoring"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact beyond that: the returned formula is live and must be re-read rather than cached or hardcoded, implying values can change between calls. It does not say how often scoring rules change or whether different calls can return different weights for different contexts.

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?

Two short sentences, front-loaded with the payload contents and followed by the operational constraint. Nothing is padded and the 'never hardcode b' warning is worth its words given the risk of acting on stale constants.

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 and zero parameters, the description only needs to convey purpose, when to call, and any volatility caveat, all of which it does. The main gap is that FIT/UNQ/INOV are unexpanded acronyms an agent may not be able to interpret before calling.

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 zero parameters, so per the baseline there is no parameter semantics to explain and the description owes nothing here. The mention of the `weights.score_multiple_constant` path is return-shape context rather than parameter guidance, and it is helpful without being required.

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 names a specific verb and resource set: returning the live payout formula, the score_multiple_constant `b`, and the FIT/UNQ/INOV scoring rules. That is far more concrete than the sibling utilities (get_capabilities, get_health, whoami), so an agent can tell this is the scoring-semantics lookup tool. It stops short of an explicit 'not to be confused with X' statement, so a 4 rather than a 5.

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 an actionable timing rule: call this to read `weights.score_multiple_constant` before self-scoring offline, and never hardcode `b`. That is a clear use condition tied to a concrete workflow. There is no explicit when-not guidance or stated alternative, which keeps it below 5.

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

Deploy Server

Other Tools