Skip to main content
Glama

cost-seg-smart

by com.costsegsmart

get_cost_seg_payment_link

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoOptional. Property ZIP code (5-digit or ZIP+4).
cityNoOptional. Property city. Used for the report cover page and metro-specific cost adjustments.
nameNoOptional. Buyer's full name for the report cover page.
sqftNoOptional. Building square footage. Improves cost-per-square-foot accuracy in the final report.
stateNoOptional. Two-letter US state code (e.g. 'CA', 'TX'). Used for state-tax adjustments where applicable.
addressNoOptional. Property street address. Improves report accuracy via county parcel data lookup post-purchase.
bedroomsNoOptional. Number of bedrooms (residential only).
bathroomsNoOptional. Number of bathrooms (residential only). Half-baths count as 0.5.
year_builtNoOptional. Year the property was originally constructed. Drives era-specific component cost adjustments.
buyer_emailNoOptional. Pre-fills the email field on the Stripe Checkout page. If omitted, Stripe collects it from the buyer at checkout.
property_typeYesProperty type identifier. Must match one of the enum values supported by get_cost_seg_quote.
purchase_priceYesProperty purchase price in US dollars. Minimum $25,000. Pricing tier is computed from this value.
acquisition_dateNoStrongly 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_attributionNoOptional. 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_dateNoStrongly 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

TableJSON Schema
NameRequiredDescriptionDefault
tierNoPresent only when the property is in the institutional custom-quote tier (purchase_price >= $25M).
messageNoPresent only for the institutional tier. Human-readable explanation to surface to the buyer.
currencyNoAlways 'USD' when present.
next_stepNoHuman-readable instruction for the agent's next action.
agent_nameNoAgent name as it appears in the buyer's checkout disclaimer.
disclaimerNoFull liability disclaimer embedded in the Stripe Checkout description. Show this to the buyer alongside the link.
study_costNoStudy cost in USD the buyer will be charged. Present only for fixed-price tiers.
contact_emailNoPresent only for the institutional tier. Route the buyer here for a custom-scoped engagement quote.
property_typeNoEcho of the requested property_type.
purchase_priceNoEcho of the requested purchase_price.
agent_order_refNoInternal correlation ID for this agent-initiated order.
payment_link_urlNoStripe Checkout URL for the buyer to click. Null for the institutional custom-quote tier — when null, see contact_email.
stripe_session_idNoStripe Checkout Session ID (cs_live_... or cs_test_...). Present only when payment_link_url is non-null.
property_type_labelNoHuman-readable property type label.

TDQS

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.

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