A
licenseA
qualityC
maintenanceProvides aggregated municipal development costs for US jurisdictions, including impact fees and utility connection charges, enabling AI agents to assess building feasibility quickly.
Last updated
14
12
MIT
cost-seg-smart
Server Details
Cost segregation study pricing and Year-1 depreciation/tax-savings estimates for US properties.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- jonhersh/cost-seg-smart-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.5/5.0
Tool DescriptionsA
Average 4.6/5 across 2 of 2 tools scored.
Server CoherenceA
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.
Available Tools
2 toolsget_cost_seg_payment_linkAInspect
Generate a Stripe Checkout URL for a human buyer to purchase a Cost Seg Smart cost segregation study. Returns a payment_link_url plus the study cost, property metadata, and a liability disclaimer naming the calling agent. The buyer must review the URL and authorize payment in their browser — this tool does not charge a card directly. Always call get_cost_seg_quote first and confirm the price with the buyer before generating the link. Side effect: creates a real Stripe Checkout Session.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| zip | No | Optional. Property ZIP code (5-digit or ZIP+4). | |
| city | No | Optional. Property city. Used for the report cover page and metro-specific cost adjustments. | |
| name | No | Optional. Buyer's full name for the report cover page. | |
| sqft | No | Optional. Building square footage. Improves cost-per-square-foot accuracy in the final report. | |
| state | No | Optional. Two-letter US state code (e.g. 'CA', 'TX'). Used for state-tax adjustments where applicable. | |
| address | No | Optional. Property street address. Improves report accuracy via county parcel data lookup post-purchase. | |
| bedrooms | No | Optional. Number of bedrooms (residential only). | |
| bathrooms | No | Optional. Number of bathrooms (residential only). Half-baths count as 0.5. | |
| year_built | No | Optional. Year the property was originally constructed. Drives era-specific component cost adjustments. | |
| buyer_email | No | Optional. Pre-fills the email field on the Stripe Checkout page. If omitted, Stripe collects it from the buyer at checkout. | |
| property_type | Yes | Property type identifier. Must match one of the enum values supported by get_cost_seg_quote. | |
| purchase_price | Yes | Property purchase price in US dollars. Minimum $25,000. Pricing tier is computed from this value. | |
| acquisition_date | No | Strongly recommended. ISO 'YYYY-MM-DD'. The date the buyer PURCHASED the property (closing/recorded transfer date), which may differ from placed_in_service_date. Both dates together set the bonus-depreciation rate; omitting both makes the study assume TODAY, which yields the maximum rate and holds the order for human review. Ask the buyer. | |
| agent_attribution | No | Optional. Overrides the X-Agent-Name request header. Use the user-visible name of your agent (e.g. 'Claude', 'ChatGPT', 'Cursor') so the buyer's checkout disclaimer correctly identifies who prepared the order. Establishes a chargeback-defense paper trail. | |
| placed_in_service_date | No | Strongly recommended. ISO 'YYYY-MM-DD'. The date the property was placed in service (available for rent or use). Together with acquisition_date this determines the bonus-depreciation RATE, which is the single largest driver of the Year-1 deduction. If you omit both dates the study assumes TODAY, which yields the maximum bonus rate — the order is then held for human review rather than delivered. Ask the buyer for this date. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| tier | No | Present only when the property is in the institutional custom-quote tier (purchase_price >= $25M). |
| message | No | Present only for the institutional tier. Human-readable explanation to surface to the buyer. |
| currency | No | Always 'USD' when present. |
| next_step | No | Human-readable instruction for the agent's next action. |
| agent_name | No | Agent name as it appears in the buyer's checkout disclaimer. |
| disclaimer | No | Full liability disclaimer embedded in the Stripe Checkout description. Show this to the buyer alongside the link. |
| study_cost | No | Study cost in USD the buyer will be charged. Present only for fixed-price tiers. |
| contact_email | No | Present only for the institutional tier. Route the buyer here for a custom-scoped engagement quote. |
| property_type | No | Echo of the requested property_type. |
| purchase_price | No | Echo of the requested purchase_price. |
| agent_order_ref | No | Internal correlation ID for this agent-initiated order. |
| payment_link_url | No | Stripe Checkout URL for the buyer to click. Null for the institutional custom-quote tier — when null, see contact_email. |
| stripe_session_id | No | Stripe Checkout Session ID (cs_live_... or cs_test_...). Present only when payment_link_url is non-null. |
| property_type_label | No | Human-readable property type label. |
Tool Definition Quality
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses the critical real-world side effect: 'Side effect: creates a real Stripe Checkout Session.' It also explains that the buyer must review and authorize payment in their browser and that a liability disclaimer names the calling agent, adding valuable behavioral context.
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?
The description is front-loaded and efficient: purpose, return value, buyer authorization requirement, prerequisite call, and side effect. Each of the five sentences provides distinct, actionable information with no filler or redundancy.
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 complexity of a payment-creation tool, the description covers purpose, return shape, buyer action, prerequisite ordering, and side effects. The output schema and rich input schema handle the remaining details, so the description is contextually complete for an agent to select and invoke it correctly.
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?
All 15 parameters are fully described in the input schema, so the description doesn't need to repeat them. It adds general context (returns study cost, property metadata, disclaimer) but no per-parameter semantics beyond what the schema already provides, which aligns with the baseline for high schema coverage.
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 states the exact action: 'Generate a Stripe Checkout URL for a human buyer to purchase a Cost Seg Smart cost segregation study.' It also distinguishes itself from the sibling get_cost_seg_quote by framing this as payment-link generation and instructing the caller to use the quote tool first.
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?
The description explicitly says when to use the tool: 'Always call get_cost_seg_quote first and confirm the price with the buyer before generating the link.' It also clarifies a key limitation—'this tool does not charge a card directly' and requires buyer authorization in the browser—which defines the appropriate use context versus other payment approaches.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_cost_seg_quoteARead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tax_bracket | No | Optional. 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_type | Yes | Property 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_price | Yes | Property 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
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| currency | Yes | Always 'USD' — Cost Seg Smart is US-only. |
| next_step | Yes | Human-readable instruction for the agent's next call. |
| disclaimer | Yes | Standard estimate disclaimer to show the buyer. |
| study_cost | No | Study cost in USD. Null for the institutional custom-quote tier (price >= $25M) — see study_cost_tier. |
| roi_multiple | No | Year-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_type | Yes | Echo of the requested property_type. |
| purchase_price | Yes | Echo of the requested purchase_price (USD). |
| study_cost_tier | Yes | '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_label | Yes | Human-readable label (e.g. 'Short-Term Rental'). |
| tax_savings_year_one | No | Estimated Year-1 federal tax savings in USD = deduction_estimate_year_one × tax_bracket. Null when tax_bracket was not provided. |
| deduction_estimate_year_one | Yes | Estimated 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+). |
Tool Definition Quality
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides real tax calculations for US, Canada, Australia, and UK income, property, and dividend taxes using up-to-date local data with no API keys required.Last updated731MIT
- AlicenseAqualityDmaintenanceAI-powered property intelligence for instant zoning analysis, buildability assessments, ADU eligibility, flood risk, and development feasibility reports for any US address.Last updated51MIT
costkits-mcpofficial
AlicenseAqualityAmaintenanceProvides live US healthcare cost data including procedure cost estimates, provider pricing, insurance coverage rules, and medical bill analysis using real hospital transparency and CMS data.Last updated12119MIT