Sell My Company Data

Estimate data licensing value

estimate_data_value

Read-onlyIdempotent

Calculates an indicative data licensing range from headcount, founding year, region and number of business systems. Smaller companies receive a clearly labelled rough estimate. Record volumes do not currently affect the calculation. Returns a link that opens the website calculator with the same inputs. Does not submit an enquiry. Usage metadata is recorded.

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": {
      "employees": "<employees>",
      "founded_year": "<founded_year>",
      "country": "<country>",
      "systems": "<systems>"
    },
    "name": "estimate_data_value"
  }
}

Input Schema

Name	Required	Description
`country`	Yes	Where the company is based: us, ca (Canada), uk, eu, anz (Australia or New Zealand), other.
`systems`	Yes	One entry per system that holds company data. May be empty if unknown.
`employees`	Yes	Approximate number of staff.
`founded_year`	Yes	Year the company was founded.
`slack_public_share`	No	Share of Slack channels that are public. The value no_slack means the company does not use Slack.

Output Schema

Name	Required	Description
`basis`	No
`range`	No
`capped`	No
`region`	No
`caveats`	Yes
`low_usd`	No
`estimate`	Yes	Always true. This is an estimate.
`headline`	Yes
`high_usd`	No
`below_bar`	No	true when the company is below the size most buyers target and the figure is a rough band.
`next_step`	Yes
`qualifies`	Yes
`disclaimer`	Yes
`estimate_url`	No	Link to the website calculator with the same inputs filled in.
`offer_prompt`	No	Owner-facing sentence explaining how to request offers.
`systems_counted`	No
`years_in_business`	No
`what_would_move_it`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

removedOutput schema / properties / how_it_works

Removed value: -{
-  "description": "How data is handled if the owner goes ahead.",
-  "type": "string"
-}

Changed1 schema field changedOct 27, 2026

addedOutput schema / properties / how_it_works

Added value: +{
+  "description": "How data is handled if the owner goes ahead.",
+  "type": "string"
+}

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / offer_prompt

Added value: +{
+  "description": "Owner-facing sentence explaining how to request offers.",
+  "type": "string"
+}

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / estimate_url

Added value: +{
+  "description": "Link to the website calculator with the same inputs filled in.",
+  "type": "string"
+}

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / slack_public_share / description

Previous value: -"Share of Slack channels that are public. Use no_slack if they do not use Slack."New value: +"Share of Slack channels that are public. The value no_slack means the company does not use Slack."

changedInput schema / properties / systems / items / properties / measured / description

Previous value: -"true if the figure is a count the user had you gather, false if the user gave an estimate."New value: +"true if the figure is a measured count, false if it is an estimate provided by the user."

First observedOct 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them: it discloses the return shape (a link that opens the website calculator with the same inputs), that no enquiry is submitted, that small-company results are rough and labelled, and that usage metadata is recorded. That last point is a privacy disclosure an agent could not infer from structured fields.

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

Conciseness5/5

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

Six short sentences, each carrying distinct information — inputs, estimate quality, a calculation caveat, return behavior, non-submission, and telemetry. The core purpose is front-loaded with no filler.

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?

An output schema exists so return values needn't be spelled out, and the description still explains the link behavior. The only gap is slack_public_share, which is never mentioned, so an agent has no narrative context for why that optional parameter is collected.

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

Parameters4/5

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

With 100% schema coverage the baseline is 3, but the description adds real semantics beyond the schema: it names which fields actually drive the calculation and explicitly states 'Record volumes do not currently affect the calculation,' saving an agent from over-populating volume fields. It omits any mention of slack_public_share, leaving one parameter unexplained.

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 ('Calculates an indicative data licensing range') plus the exact inputs that drive it, so the agent knows precisely what it produces. It also carves itself away from the sibling request_offer with 'Does not submit an enquiry.'

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?

'Does not submit an enquiry' clearly excludes the enquiry path (request_offer), and 'Smaller companies receive a clearly labelled rough estimate' sets expectations about output quality. It stops short of naming siblings outright or stating when the tool is inappropriate, but the contextual guidance is clear.

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

All Sell My Company Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?