Intangible Asset Valuation

Technology Assets

valuation_technology

Read-onlyIdempotent

Value developed technology, software, data assets, and platforms using method-specific cost, income, and network-effect formulas for intangible asset valuation.

Instructions

Technology assets: developed technology under life-cycle risk, software under cost and income, data assets with a quality adjustment, and platforms with network effects. Method selects the formula. Use for developed technology, software, data, and platform intangibles; developed_technology and software blend cost and income evidence. For patents, trademarks, copyrights, and trade secrets use valuation_ip; for customer relationships use valuation_customer. Per method: developed_technology needs rd_costs + life_cycle_stage + competitive_advantage + discount_rate + cash_flow_projections; software needs development_cost + maintenance_cost + user_base + revenue_model + useful_life + discount_rate; data_asset needs acquisition_cost + quality_score + revenue_contribution + useful_life + discount_rate; platform needs network_size + network_effects_coefficient + revenue_per_user + growth_rate + discount_rate. cash_flow_projections for developed_technology run over the remaining useful life. Only method is required; other parameters are method-dependent, so supply those named for the selected method and omit the rest (documented defaults apply where defined). Pure arithmetic: no I/O and no external calls, and numeric results are returned rounded to 2 decimals. Parameters belonging to other methods of this tool are accepted and ignored. Supplying an unknown method, or leaving unset a parameter that the chosen method requires, returns an error instead of a value.

Input Schema

TableJSON Schema

Name	Required	Description
`method`	Yes	Formula to apply. Options: developed_technology = Cost and income value adjusted for life-cycle stage.; software = Software value from development, maintenance, and revenue.; data_asset = Quality-adjusted revenue contribution plus acquisition cost.; platform = Network-effect revenue grown and discounted.
`rd_costs`	No	Cumulative research and development costs, in currency units.
`user_base`	No	Number of users.
`growth_rate`	No	Per-period growth rate as a decimal (0.03 = 3%).
`useful_life`	No	Useful life in years n.
`network_size`	No	Number of network participants.
`discount_rate`	No	Per-period discount rate as a decimal (0.10 = 10%).
`quality_score`	No	Data quality score, in [0,1].
`revenue_model`	No	Revenue model, e.g. {"subscription_price": 20, "paying_users": 10000}.
`acquisition_cost`	No	Cost to acquire the data, in currency units.
`development_cost`	No	Development or acquisition cost, in currency units.
`life_cycle_stage`	No	Life-cycle stage, e.g. "growth", "mature", "decline".
`maintenance_cost`	No	Annual maintenance cost, in currency units.
`revenue_per_user`	No	Revenue per user, in currency units.
`revenue_contribution`	No	Annual revenue contribution, in currency units.
`cash_flow_projections`	No	Projected after-tax cash flows per period t=1..n, in currency units.
`competitive_advantage`	No	Years of competitive advantage.
`network_effects_coefficient`	No	Network-effects coefficient scaling revenue with network size.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Error message when the call fails.
`steps`	No	Intermediate calculation steps for traceability (one string per step).
`value`	Yes	Computed valuation, rate, or metric.
`method`	No	Formula / method name that produced the result.
`assumptions`	No	Modelling assumptions applied (list of strings or key/value object).
`formula_reference`	No	Mathematical formula or reference applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.4Sep 30, 2026

changedOutput schema / properties / steps / description

Previous value: -"Intermediate calculation steps for traceability."New value: +"Intermediate calculation steps for traceability (one string per step)."

removedOutput schema / properties / steps / items / type
```
Removed value: -"object"
```

First observedv0.1.0Sep 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: pure arithmetic with no I/O or external calls, results rounded to 2 decimals, string-method errors, missing-required-param errors, and the notable rule that parameters belonging to other methods are accepted and ignored. That last point is behavior an agent cannot infer from the schema.

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 purpose and routing, then the per-method parameter lists. Efficient and every sentence carries content, but the dense run-on parameter enumeration is long and slightly harder to scan than it could be.

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

Completeness5/5

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

For an 18-parameter, method-dispatching calculator with an output schema, the description covers routing, per-method inputs, error behavior, rounding, and extraneous-parameter handling. Return values need no explanation since an output schema exists.

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

Parameters5/5

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

Although schema coverage is 100%, the schema does not say which parameters each method requires. The description supplies the exact method-to-parameter mapping for all four methods, notes that only method is required, that others have documented defaults, and that foreign-method params are ignored.

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?

The description names the specific resource (technology intangibles) and enumerates the four valuation methods it covers, then explicitly distinguishes itself from valuation_ip and valuation_customer by naming those siblings. An agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

It states when to use this tool (developed technology, software, data, platform intangibles) and gives explicit when-not guidance by naming the correct alternatives for patents/trademarks/copyrights/trade secrets (valuation_ip) and customer relationships (valuation_customer).

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

Deploy Server