Skip to main content
Glama

cost-seg-smart

by com.costsegsmart

get_cost_seg_quote

Read-onlyIdempotent

Quote a CPA-ready cost segregation study for a US real estate property. Returns the study cost in USD, estimated Year-1 accelerated depreciation, and (when a tax bracket is provided) Year-1 tax savings and ROI on the study fee. Pure tier-matrix lookup — no engine run, no charge to the buyer, safe to call repeatedly. Use this before generating a payment link so you can confirm the price with the buyer. Does not provide tax advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tax_bracketNoOptional. Buyer's federal marginal tax bracket. Accepts decimal form (0.0-0.6, e.g. 0.32 for 32%) OR whole-number percent (0-60). When provided, response includes tax_savings_year_one and roi_multiple. When omitted, response only includes the deduction estimate.
property_typeYesProperty type identifier. Determines the pricing tier and the default Year-1 reclassification percentage. Residential types (sfr, str, condo, condo_str, adu) reclassify ~22-30%; small multifamily (duplex/triplex/fourplex) ~27%; commercial varies by subtype (~18-30%).
purchase_priceYesProperty purchase price in US dollars. Minimum $25,000. The pricing tier is computed from this value. Properties >= $25M fall in the institutional custom-quote tier.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyYesAlways 'USD' — Cost Seg Smart is US-only.
next_stepYesHuman-readable instruction for the agent's next call.
disclaimerYesStandard estimate disclaimer to show the buyer.
study_costNoStudy cost in USD. Null for the institutional custom-quote tier (price >= $25M) — see study_cost_tier.
roi_multipleNoYear-1 return on the study fee = tax_savings_year_one / study_cost, rounded to integer. Null when tax_bracket was not provided or study_cost is null.
property_typeYesEcho of the requested property_type.
purchase_priceYesEcho of the requested purchase_price (USD).
study_cost_tierYes'fixed_price' = study_cost is a real USD amount. 'institutional_custom' = property is in the $25M+ tier; route the buyer to support@costsegsmart.com.
property_type_labelYesHuman-readable label (e.g. 'Short-Term Rental').
tax_savings_year_oneNoEstimated Year-1 federal tax savings in USD = deduction_estimate_year_one × tax_bracket. Null when tax_bracket was not provided.
deduction_estimate_year_oneYesEstimated Year-1 accelerated depreciation in USD, computed as purchase_price × (1 - 0.18 land) × reclass_pct[property_type]. Assumes 100% bonus depreciation per OBBBA §168(k) (2025+).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint true. The description adds that it is a pure tier-matrix lookup with no engine run and no charge, reinforcing the safe-to-call nature. No contradictions.

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?

Five sentences, each serving a distinct purpose: purpose, returns, behavior, usage, and disclaimer. No redundancy. Well-structured and front-loaded.

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?

Given the tool has an output schema and good annotations, the description provides sufficient context: purpose, what it returns, behavioral traits, and usage guidance. It covers all necessary aspects for an agent to decide when and how to use it.

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?

The schema covers 100% of parameters with descriptions. The tool description adds context by linking the parameters to the output (e.g., tax_bracket controls whether tax savings are returned, property_type and purchase_price determine tier). This adds meaningful context beyond the schema.

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 clearly states the tool quotes a cost segregation study, lists what it returns (study cost, depreciation, tax savings), and distinguishes from the sibling tool by noting it is used before generating a payment link. It uses a specific verb 'Quote' and identifies the resource 'cost segregation study'.

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?

The description explicitly says to use this before generating a payment link to confirm the price. It also notes the tool is a pure matrix lookup, safe to call repeatedly, implying it can be used for exploration. It does not explicitly state when not to use, but the sibling tool name suggests an alternative for payment.

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

All cost-seg-smart toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

The two tools have completely distinct purposes: one quotes a price and depreciation estimate, the other generates a Stripe payment link. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools follow the exact same `get_cost_seg_` prefix with a descriptive noun (`quote` vs `payment_link`), forming a consistent verb_noun pattern.

Tool Count3/5

With only two tools, the server feels thin, but the narrow scope of quoting and payment fits this small count. It's on the borderline of being under-scoped.

Completeness4/5

The core sales workflow (quote, confirm price, generate payment link) is fully covered. A minor gap is the lack of post-payment status tracking or order verification, but the two tools serve the stated purpose well.

Resources