FreeDailyPro Business Documents

business_profit_margin

Read-onlyIdempotent

Profit margin calculator

Input Schema

Name	Required	Description	Default
`cost`	No
`price`	No
`profit`	No
`shipping`	No
`marginPct`	No
`markupPct`	No
`acquisition`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026
- addedInput schema / properties / cost / minimum
```
Added value: +0
```
- addedInput schema / properties / price / minimum
```
Added value: +0
```
Changed6 schema fields changedOct 31, 2026
- addedInput schema / properties / acquisition
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / marginPct
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / markupPct
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / profit
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / shipping
```
Added value: +{
+  "type": "number"
+}
```
- removedInput schema / required
```
Removed value: -[
-  "cost",
-  "price"
-]
```
First observedOct 24, 2026

TDQS

D1.6/5.0

Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. However, the description adds no behavioral context about how the calculation works, which parameter combinations are valid, whether inputs are mutually exclusive, or what the tool returns.

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

Conciseness2/5

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

The description is only three words, which is concise but severely under-specified rather than efficiently structured. It does not front-load any useful invocation or scoping information.

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

Completeness1/5

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

For a tool with seven undocumented optional parameters and no output schema, the description is completely inadequate. It does not explain valid input combinations, the calculation logic, expected outputs, or how to choose between this and closely related sibling tools.

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

Parameters1/5

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

The schema has seven parameters with 0% description coverage, including ambiguous fields like profit, marginPct, markupPct, and acquisition. The description provides no information about what these parameters mean or how they relate, so it completely fails to compensate for the missing schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Profit margin calculator' essentially restates the tool name business_profit_margin and adds no distinguishing scope. It does not differentiate this from the very similar sibling business_product_margin or clarify what kind of profit-margin calculation it performs.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, when not to use it, or which alternative sibling tools such as business_product_margin or business_break_even should be preferred. The agent is left to infer usage entirely from the name.

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

All FreeDailyPro Business Documents 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?