Skip to main content
Glama
collapseindex

CI-1T Prediction Stability Engine

interpret_scores

Generate a statistical breakdown of raw prediction scores, providing count, mean, std, min, max, and per-value normalized data. Accepts floats (0.0–1.0) or Q0.16 integers (0–65535).

Instructions

Analyze raw prediction scores with statistical breakdown — no API call, no auth, no credits. Response: { count, mean, std, min, max, breakdown: [{ index, raw, normalized }] }. Accepts floats (0.0–1.0) or Q0.16 integers (0–65535) — auto-detects. For full stability classification (Stable/Drift/Flip/Collapse), pass scores to the evaluate tool instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scoresYesArray of scores — floats (0.0–1.0) or Q0.16 integers (0–65535)

Implementation Reference

  • The interpret_scores tool handler. Accepts an array of scores (float or Q0.16), computes count/mean/std/min/max, and returns a per-index breakdown with raw and normalized values. No API call, no auth required.
    server.tool(
      "interpret_scores",
      "Analyze raw prediction scores with statistical breakdown — no API call, no auth, no credits. Response: { count, mean, std, min, max, breakdown: [{ index, raw, normalized }] }. Accepts floats (0.0–1.0) or Q0.16 integers (0–65535) — auto-detects. For full stability classification (Stable/Drift/Flip/Collapse), pass scores to the evaluate tool instead.",
      {
        scores: z.array(z.number().min(0).max(65535)).min(1).max(300).describe("Array of scores — floats (0.0–1.0) or Q0.16 integers (0–65535)"),
      },
      async ({ scores }) => {
        const q16 = toQ16(scores);
        const normalized = q16.map((s) => Math.min(s, Q16) / Q16);
        const mean = normalized.reduce((a, b) => a + b, 0) / normalized.length;
        const std = Math.sqrt(normalized.reduce((a, b) => a + (b - mean) ** 2, 0) / normalized.length);
        const min = Math.min(...normalized);
        const max = Math.max(...normalized);
    
        const breakdown = normalized.map((n, i) => ({
          index: i,
          raw: q16[i],
          normalized: Number(n.toFixed(4)),
        }));
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(
                {
                  count: q16.length,
                  mean: Number(mean.toFixed(4)),
                  std: Number(std.toFixed(4)),
                  min: Number(min.toFixed(4)),
                  max: Number(max.toFixed(4)),
                  breakdown,
                  note: "For stability classification (Stable/Drift/Flip/Collapse), run these through the evaluate tool.",
                },
                null,
                2
              ),
            },
          ],
        };
      }
    );
  • Zod input schema for interpret_scores. Accepts an array of 1–300 numbers between 0 and 65535 (covers both floats and Q0.16).
    scores: z.array(z.number().min(0).max(65535)).min(1).max(300).describe("Array of scores — floats (0.0–1.0) or Q0.16 integers (0–65535)"),
  • src/index.ts:825-866 (registration)
    Registration of interpret_scores via server.tool() on the MCP server object. Registers it under the name "interpret_scores".
    server.tool(
      "interpret_scores",
      "Analyze raw prediction scores with statistical breakdown — no API call, no auth, no credits. Response: { count, mean, std, min, max, breakdown: [{ index, raw, normalized }] }. Accepts floats (0.0–1.0) or Q0.16 integers (0–65535) — auto-detects. For full stability classification (Stable/Drift/Flip/Collapse), pass scores to the evaluate tool instead.",
      {
        scores: z.array(z.number().min(0).max(65535)).min(1).max(300).describe("Array of scores — floats (0.0–1.0) or Q0.16 integers (0–65535)"),
      },
      async ({ scores }) => {
        const q16 = toQ16(scores);
        const normalized = q16.map((s) => Math.min(s, Q16) / Q16);
        const mean = normalized.reduce((a, b) => a + b, 0) / normalized.length;
        const std = Math.sqrt(normalized.reduce((a, b) => a + (b - mean) ** 2, 0) / normalized.length);
        const min = Math.min(...normalized);
        const max = Math.max(...normalized);
    
        const breakdown = normalized.map((n, i) => ({
          index: i,
          raw: q16[i],
          normalized: Number(n.toFixed(4)),
        }));
    
        return {
          content: [
            {
              type: "text" as const,
              text: JSON.stringify(
                {
                  count: q16.length,
                  mean: Number(mean.toFixed(4)),
                  std: Number(std.toFixed(4)),
                  min: Number(min.toFixed(4)),
                  max: Number(max.toFixed(4)),
                  breakdown,
                  note: "For stability classification (Stable/Drift/Flip/Collapse), run these through the evaluate tool.",
                },
                null,
                2
              ),
            },
          ],
        };
      }
    );
Behavior4/5

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

Despite no annotations, the description discloses response structure, input auto-detection, and that it makes no external calls. It does not mention any potential side effects or logging, but for a simple stateless tool this is sufficient.

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?

Extremely concise: two sentences cover purpose, behavior, input, output, and alternatives. Front-loaded with key info.

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?

Given no output schema, the description fully documents the return value structure. It covers all needed context: what it does, what it returns, acceptable inputs, and alternative tool. No gaps.

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 100% but description adds value by explaining auto-detection of float vs integer, and details the response breakdown. This goes beyond just repeating the schema.

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 clearly states the verb 'Analyze' and the resource 'raw prediction scores with statistical breakdown'. It distinguishes itself from siblings like evaluate and convert_scores by specifying the response structure and input types.

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 says when to use this tool: for statistical breakdown, and when not: for full stability classification, use evaluate tool. Also notes no API call, no auth, no credits.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/collapseindex/ci-1t-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server