Skip to main content
Glama

Software cost comparison

toolfound_software_cost_comparison
Read-onlyIdempotent

Normalize two software prices to a first-year cost using seats, billing periods, setup fees, and expected usage charges. Returns an evidence-bounded result and the canonical web tool URL.

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": {
      "seats": "<seats>",
      "aName": "<aName>",
      "aPrice": "<aPrice>",
      "aBilling": "<aBilling>",
      "bName": "<bName>",
      "bPrice": "<bPrice>",
      "bBilling": "<bBilling>"
    },
    "name": "toolfound_software_cost_comparison"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNameYesLabel for the first option, used in the result.
bNameYesLabel for the second option, used in the result.
seatsYesNumber of people who will need a licence, as a whole number. Both options are priced for this same count.
aPriceYesOption A list price per seat in US dollars as a plain number. It is per month when aBilling is monthly, per year when annual, and a single payment when one-time.
aSetupNoOptional one-time setup or onboarding fee for option A in US dollars. Defaults to 0 when omitted.
aUsageNoOptional expected usage-based charges for option A in US dollars per month, such as overages. Counted for 12 months. Defaults to 0.
bPriceYesOption B list price per seat in US dollars as a plain number. It is per month when bBilling is monthly, per year when annual, and a single payment when one-time.
bSetupNoOptional one-time setup or onboarding fee for option B in US dollars. Defaults to 0 when omitted.
bUsageNoOptional expected usage-based charges for option B in US dollars per month, such as overages. Counted for 12 months. Defaults to 0.
aBillingYesHow option A's price is charged: monthly prices are multiplied by 12 for the first year, annual and one-time prices are counted once.
bBillingYesHow option B's price is charged: monthly prices are multiplied by 12 for the first year, annual and one-time prices are counted once.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / aBilling / description
      Added value: +"How option A's price is charged: monthly prices are multiplied by 12 for the first year, annual and one-time prices are counted once."
    • addedInput schema / properties / aName / description
      Added value: +"Label for the first option, used in the result."
    • addedInput schema / properties / aPrice / description
      Added value: +"Option A list price per seat in US dollars as a plain number. It is per month when aBilling is monthly, per year when annual, and a single payment when one-time."
    • addedInput schema / properties / aSetup / description
      Added value: +"Optional one-time setup or onboarding fee for option A in US dollars. Defaults to 0 when omitted."
    • addedInput schema / properties / aUsage / description
      Added value: +"Optional expected usage-based charges for option A in US dollars per month, such as overages. Counted for 12 months. Defaults to 0."
    • addedInput schema / properties / bBilling / description
      Added value: +"How option B's price is charged: monthly prices are multiplied by 12 for the first year, annual and one-time prices are counted once."
    • addedInput schema / properties / bName / description
      Added value: +"Label for the second option, used in the result."
    • addedInput schema / properties / bPrice / description
      Added value: +"Option B list price per seat in US dollars as a plain number. It is per month when bBilling is monthly, per year when annual, and a single payment when one-time."
    • addedInput schema / properties / bSetup / description
      Added value: +"Optional one-time setup or onboarding fee for option B in US dollars. Defaults to 0 when omitted."
    • addedInput schema / properties / bUsage / description
      Added value: +"Optional expected usage-based charges for option B in US dollars per month, such as overages. Counted for 12 months. Defaults to 0."
    • addedInput schema / properties / seats / description
      Added value: +"Number of people who will need a licence, as a whole number. Both options are priced for this same count."
  2. Added

TDQS

A3.6/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. The description adds only that the result is 'evidence-bounded' and includes 'the canonical web tool URL' — a useful but thin behavioral note; with an output schema present, the return shape needs no further disclosure.

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?

Two sentences, zero filler, with the operation front-loaded and the output summary trailing. Nothing in it is redundant or padded.

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?

For a complex 11-parameter tool, the description plus rich annotations, a fully documented schema and an output schema together give an agent enough to call it correctly. The only residual gap is guidance on when this comparison is the right tool versus adjacent cost/planning siblings.

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 every one of the 11 parameters is already documented in detail, including defaults for optional setup and usage fees and the monthly/annual/one-time multiplier semantics. The description restates the same factors only as a list, adding framing (first-year normalization) but no parameter meaning absent from the schema, so the baseline 3 applies.

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 names a specific verb and resource ('Normalize two software prices to a first-year cost') and enumerates the modeling inputs (seats, billing periods, setup fees, usage charges). It is unambiguous and no sibling in the catalog overlaps with this comparison operation, so the agent can identify it without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied by the computation described: an agent can infer this is for comparing two purchase options on a first-year basis. There is no explicit when-to-use versus when-not, and no mention of related siblings such as toolfound_sponsorship_break_even for other cost-modeling questions.

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.

Resources