Skip to main content
Glama

Primer Market Systems (MSD) & DCED Engine

calculate_dced_attribution

Read-onlyIdempotent

Calculate DCED-compliant attributable Net Additional Income (NAI), deadweight, displacement, substitution, systemic copycat crowding-in, and full-time equivalent (FTE) employment.

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": {
      "beneficiaries_reached": "<beneficiaries_reached>",
      "gross_additional_income_per_beneficiary": "<gross_additional_income_per_beneficiary>",
      "deadweight_pct": "<deadweight_pct>",
      "displacement_pct": "<displacement_pct>",
      "substitution_pct": "<substitution_pct>",
      "crowding_in_multiplier": "<crowding_in_multiplier>",
      "direct_partner_jobs_created": "<direct_partner_jobs_created>",
      "additional_labor_days_per_beneficiary": "<additional_labor_days_per_beneficiary>",
      "program_intervention_cost": "<program_intervention_cost>"
    },
    "name": "calculate_dced_attribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
deadweight_pctYesAdoption percentage that would have occurred without the project (0-100%).
displacement_pctYesIncome gains displacing existing local businesses (0-100%).
substitution_pctYesForgone income from abandoned alternative crops (0-100%).
working_days_per_fteNoBenchmark workdays per full-time equivalent job.
beneficiaries_reachedYesVerified adopting farmers or micro-enterprises.
crowding_in_multiplierYesRatio capturing competitor imitation (1.0 = none, 1.25 = 25% copycat expansion).
program_intervention_costYesTotal donor budget allocated to intervention ($).
direct_partner_jobs_createdYesSalaried jobs created by commercial lead firm.
additional_labor_days_per_beneficiaryYesExtra casual on-farm labor days demanded per year.
gross_additional_income_per_beneficiaryYesAnnual gross income increase per adopter ($/yr).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that the operation is a DCED-standard computation combining several adjustment factors, which is useful framing beyond the annotations. It still omits the assumptions baked into the calculation (e.g. how factors are applied, units of the FTE conversion, rounding) and gives no sense of the return shape.

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?

A single dense sentence with zero filler, front-loaded on the verb and the standard being complied with. The long metric enumeration is information-bearing rather than padding, though it could have been tightened into a list-friendly form.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Nine of ten parameters are required and all are documented, so input-side completeness is fine. With no output schema, however, the description never states what the calculation returns (scalar NAI, a breakdown per adjustment factor, FTE count, or a structured report), which is a meaningful gap for a pure computational tool. It is otherwise adequate for its complexity.

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% with 10 well-annotated parameters including ranges and default values (working_days_per_fte defaults to 240), so the schema carries the parameter burden. The description restates the metric names in prose but adds no formula, ordering, or constraint detail beyond what the schema already provides. Baseline 3 is appropriate.

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 uses a specific verb ('Calculate') with a named, standards-based resource ('DCED-compliant attributable Net Additional Income') and enumerates the metrics produced (deadweight, displacement, substitution, crowding-in, FTE). An agent can tell this is an economic-attribution calculator rather than a lookup tool. It does not, however, distinguish itself from the sibling 'calculate_deal', so it stops short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no reference to any alternative such as calculate_deal. The only implied context is 'DCED compliance', which an agent must infer from the description. This leaves selection between the two calculation siblings ambiguous.

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.