Skip to main content
Glama

cocomo_estimate

Read-onlyIdempotent

Estimate software effort in person-months from KLOC using LLM-adjusted COCOMO II factors, returning nominal and AI-adjusted results for planning codebase work.

Instructions

LLM-adapted COCOMO II parametric effort estimation.

Replaces traditional 17 human-labor cost drivers with 5 LLM-specific factors: reasoning complexity, context completeness, transformation impact, iterative cycles, and human oversight. Returns both nominal and LLM-adjusted person-months. Use when estimating effort for a codebase you can size in KLOC. iterative_cycles: values <= 2.0 are literal multipliers (0.5 = one-shot, 1.0 = typical debug loop, 2.0 = heavy back-and-forth); values above 2.0 are literal cycle counts, each additional cycle adding 0.1 of multiplier anchored at 2.0 (2.0 -> 2.0x, 3 -> 2.1x, 10 -> 2.8x) — monotonic with no cliff at 2.0.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kloc": "<kloc>"
    },
    "name": "cocomo_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
klocYesEstimated thousands of lines of code. Count actual code, not comments/blank lines.
projectNoOptional project/repo identifier this estimate belongs to, for cross-project analytics.
ai_nativeNoDegree of AI assistance: 0.0 = fully human, 1.0 = fully AI-native, 0.5 = hybrid. Accepts boolean for backward compatibility (true=1.0, false=0.0).
task_typeNoOptional task type for feedback matching.
session_idNoOptional session identifier (minted by a calling agent/hook) used to deduplicate repeated estimate calls for the same task within a session.
task_labelNoOptional free-text label identifying the task this estimate is for (e.g. an issue key or short title). Surfaced on get_pending_estimates output for triage.
human_oversightNoHuman review overhead multiplier. 0.5 = auto-merged, 1.0 = standard PR review, 2.0 = compliance/security review.
iterative_cyclesNoIteration overhead multiplier or literal cycle count. Multiplier scale: 0.5 = one-shot, 1.0 = typical debug loop, 2.0 = heavy back-and-forth. Values above 2.0 are accepted as literal cycle counts and normalized internally.
context_completenessNoHow complete is the context provided to the LLM? 0.5 = exhaustive specs, 1.0 = typical, 2.0 = vague requirements.
reasoning_complexityNoMultiplier for reasoning complexity of the codebase. 0.5 = trivial CRUD, 1.0 = average, 2.0 = novel algorithm/R&D.
transformation_impactNoScale of transformation relative to existing code. 0.5 = small patch, 1.0 = new module, 2.0 = architectural rewrite.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.8.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / ai_native / default
      Removed value: -1
    • addedInput schema / properties / project
      Added value: +{
      +  "description": "Optional project/repo identifier this estimate belongs to, for cross-project analytics.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / session_id
      Added value: +{
      +  "description": "Optional session identifier (minted by a calling agent/hook) used to deduplicate repeated estimate calls for the same task within a session.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / task_label
      Added value: +{
      +  "description": "Optional free-text label identifying the task this estimate is for (e.g. an issue key or short title). Surfaced on get_pending_estimates output for triage.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description does add real behavior: the output contains two figures (nominal and LLM-adjusted person-months) and iterative_cycles has a piecewise normalization above 2.0 with no cliff. It omits other operational context (whether estimates are persisted, how session_id dedupe behaves, calibration state), so it is additive but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence front-loads the purpose well, but the description then re-lists the five cost drivers that the schema already names in each parameter's description, and repeats the multiplier scale verbatim before adding the genuinely new >2.0 formula. Roughly a third of the text restates structured fields rather than earning new information.

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 11 parameters at full schema coverage and no output schema, the description carries the return-value burden and does so by naming both person-month figures. The unusual iterative_cycles input, the one thing an agent would likely get wrong, is explained in detail. Minor gaps (persistence, dedupe behavior) are covered by the schema's own parameter descriptions.

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%, so the schema already documents all 11 parameters; baseline is 3. The description adds genuine meaning only for iterative_cycles, specifying the piecewise mapping (2.0 -> 2.0x, 3 -> 2.1x, 10 -> 2.8x) that the schema merely calls 'normalized internally'. The five named factors map loosely to parameters but add no per-parameter guidance beyond what the schema states.

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?

States a specific verb and resource ('parametric effort estimation', 'Returns both nominal and LLM-adjusted person-months') and names the underlying method (COCOMO II adapted with 5 LLM-specific factors). It does not name a sibling estimator (pert_estimate, reference_class_estimate) to contrast against, so differentiation is implied by the KLOC-sizing condition rather than stated.

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?

'Use when estimating effort for a codebase you can size in KLOC' gives a clear positive selection condition, which is meaningful given several sibling estimators. There is no explicit when-not guidance or named alternative for cases where KLOC is unknown, leaving the agent to infer that the other estimators cover that case.

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