Skip to main content
Glama

How the scores and money are computed

methodology
Read-onlyIdempotent

How scores, weights, must-pass lines, missing data, the money model, the right to live and the open-data rule work, with every scale.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
reportVersionYesThe report's shape version (now 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds value by listing the specific topics covered (scales, money model, open-data rule), but it does not describe the return format, that the content is static documentation, or any other behavioral trait beyond what annotations provide.

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 a single, front-loaded sentence that efficiently lists the topics covered. It contains no wasted wording, though the list-like structure could be marginally clearer with a brief introductory phrase about the tool's role.

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?

Given the tool's simplicity (no parameters, output schema present, annotations covering safety), the description is sufficiently complete: it tells the agent what information will be returned. It does not need to explain return values because the output schema exists, but it could be slightly more explicit that the tool returns static reference material.

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 has zero parameters and the schema description coverage is 100% (empty schema). The baseline for no parameters is 4, and the description appropriately does not attempt to explain nonexistent parameters.

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 clearly states it explains how scores, weights, must-pass lines, missing data, the money model, the right to live, and the open-data rule work, with every scale. It is specific about the topics covered and distinguishes itself from data-manipulation siblings by being a reference tool, though it doesn't explicitly name alternatives.

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?

The description implies usage (call this to understand the methodology behind the other tools) but offers no explicit when-to-use or when-not-to-use guidance, and does not mention any alternatives or prerequisites.

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.