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
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Tool Definition Quality
Average 4.6/5 across 2 of 2 tools scored.
The two tools serve entirely different purposes: one provides a quote, the other generates a payment link. There is no ambiguity between them.
Both tools follow the exact pattern 'get_cost_seg_<action>', using consistent snake_case and meaningful suffixes.
With only 2 tools, the server is minimal but appropriately scoped for quoting and purchasing a cost segregation study. It could be expanded slightly (e.g., status check), but the count is reasonable.
The tools cover the essential tasks (quote and initiate purchase), but there is no way to confirm payment status or retrieve the study after purchase, leaving a notable gap.
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.
| 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 $50,000. Pricing tier is computed from this value. | |
| 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. |
Output 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the side effect of creating a Stripe Checkout Session, states it does not charge directly, and mentions the liability disclaimer. Annotations show readOnlyHint=false, consistent with mutation. No contradiction, but could add more on idempotency or failure modes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four sentences, each serving a purpose: purpose, return details, buyer action, prerequisite, side effect. No redundancy, front-loaded with main action.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With output schema and rich parameter schemas, the description covers workflow prerequisites, side effects, and buyer action. It could mention link expiration or idempotency but is sufficient for a payment link tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with detailed descriptions for each parameter. The tool description does not add parameter-level information beyond the schema, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool generates a Stripe Checkout URL for purchasing a cost segregation study, specifies the return payload, and distinguishes from the sibling get_cost_seg_quote by requiring it to be called first.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly instructs to call get_cost_seg_quote first and confirm price with buyer, and that the buyer must authorize payment in browser. It lacks an explicit when-not-to-use, but the single sibling and clear workflow make guidance strong.
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.
| 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 $50,000. The pricing tier is computed from this value. Properties >= $25M fall in the institutional custom-quote tier. |
Output 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that it's a pure tier-matrix lookup with no engine run, no charge, and safe to call repeatedly, complementing the readOnlyHint and idempotentHint annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences front-loaded with purpose, no wasted words. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given output schema exists, description doesn't need to explain returns. It covers input semantics, conditions, and relationship to payment link. Fully sufficient for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Adds meaningful context beyond schema: tax_bracket accepts decimal or percent, property_type includes example percentages, purchase_price has minimum and mentions $25M tier. Schema coverage is 100% but description enriches it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it quotes a cost segregation study, returns cost, depreciation, and optionally tax savings. Distinguishes from sibling 'get_cost_seg_payment_link' by noting it's used before generating a payment link.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use ('before generating a payment link'), and clarifies it does not provide tax advice or charge the buyer. Safe to call repeatedly, no side effects.
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!