Skip to main content
Glama

cocomo_validate

Read-onlyIdempotent

Validate a COCOMO estimation model against historical project datasets and report MAPE, bias, per-type accuracy, and recommended coefficient adjustments.

Instructions

Validate COCOMO estimation model against 195 real historical projects.

Runs the COCOMO Basic formula against projects from NASA93, COCOMO81, Albrecht, and Kemerer datasets. Reports overall MAPE, bias, per-type accuracy, and recommended coefficient adjustments. Use cocomo_ground_truth for the full multi-model benchmark across all COCOMO and AI-adjusted models.

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

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 declare readOnly/idempotent/non-destructive, so the safety bar is covered. The description adds genuinely useful behavior beyond that: it discloses the fixed 195-project corpus and the report contents (MAPE, bias, per-type accuracy, recommended coefficient adjustments), which is important given there is no output schema. It omits cost/runtime of running the benchmark, but that is minor.

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?

Front-loaded with the core action, then corpus, then outputs, then the alternative — a clean escalation. Slight redundancy in re-listing the four dataset names that the schema already enumerates.

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?

For a zero-required-param read-only validation tool, everything needed to call it is present, and the prose compensates for the absent output schema by naming the reported metrics. A note on how current the 195-project corpus is, or whether the recommended coefficient adjustments are advisory only, would close the remaining gap.

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?

With a single optional param and 100% schema description coverage, the schema already documents dataset_filter and its allowed values. The description restates the same dataset names, which corroborates but adds no new meaning such as filtering semantics or defaults.

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+resource+scope: 'Validate COCOMO estimation model against 195 real historical projects', and immediately scopes the data sources (NASA93, COCOMO81, Albrecht, Kemerer). It explicitly names the sibling it is not (cocomo_ground_truth), so an agent can route correctly without opening either schema.

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?

Gives clear context for this tool (single-model validation against a fixed historical corpus) and an explicit alternative with the condition that selects it: 'Use cocomo_ground_truth for the full multi-model benchmark.' It does not state prerequisites such as whether the model must already be calibrated, so it stops short of a full when/when-not treatment.

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