Skip to main content
Glama

cocomo_ground_truth

Read-onlyIdempotent

Validate COCOMO estimation models against 240 historical projects with known effort, comparing six model variants and reporting MAPE, MMRE, PRED(25/50), and bias by dataset and project type.

Instructions

Validate all COCOMO estimation models against 240 real historical projects with known effort.

Runs 6 models in parallel: COCOMO Basic, COCOMO II Nominal, COCOMO II + AI 12x speedup, and AI + developer profile at human/hybrid/ai_native gradients. Reports MAPE, MMRE, PRED(25), PRED(50), bias per model, with breakdowns by dataset and project type. Use cocomo_validate for a quicker Basic COCOMO-only validation pass.

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

Input Schema

NameRequiredDescriptionDefault
dataset_filterNoOptional filter to validate against specific datasets only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral detail: six models run in parallel and a specific metric set (MAPE, MMRE, PRED(25), PRED(50), bias) with per-dataset and per-project-type breakdowns. It does not mention cost or runtime of a 240-project x 6-model sweep, which is the one behavior an agent might still want to know.

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?

Four short lines, front-loaded with the core action and scope, then the model list, then the reported metrics, then the sibling routing. The model enumeration is dense but each line carries information. Minor trimming of metric redundancy would make it a 5.

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 no output schema, the description must convey what comes back, and it does by listing MAPE, MMRE, PRED(25), PRED(50), bias and the two breakdown dimensions. Given a one-parameter read-only tool, an agent has everything needed to call it and interpret the result; only runtime expectations are missing.

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

Parameters3/5

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

Schema description coverage is 100% and the single optional dataset_filter already documents the accepted dataset names, so the schema does the heavy lifting. The description's mention of 'breakdowns by dataset' implicitly explains the filter's effect but adds no syntax or format beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource (validate COCOMO estimation models) plus the exact scope: 240 historical projects with known effort, and enumerates the 6 models run, including the AI 12x speedup and the three developer-profile gradients. This is clearly distinguishable from cocomo_validate, which the description itself names as the narrower alternative.

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?

Explicitly routes the agent away from this tool when a quick Basic-COCOMO-only pass suffices: 'Use cocomo_validate for a quicker Basic COCOMO-only validation pass.' That gives a concrete selection rule against a sibling. It stops short of stating full when-to-use conditions (e.g., expected runtime or data prerequisites), so not a 5.

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