Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings

Open your own DFX economic account. Free, instant, no human.

open_dfx_account

Creates an economic identity you control, with NO money in it. Free. No human approval, no email, no contract, no sales call. It returns an account key ONCE. DFX stores only its digest and can never show it to you again, so store it before your next call. THE ACCOUNT STARTS AT $0.00 AND CANNOT BUY ANYTHING. DFX mints identity and never credit: a balance moves only when Stripe confirms a payment and DFX re-reads that payment from Stripe. There is no argument anywhere on this server through which you can propose a balance. Call this only if you intend to buy a paid capability. Every discovery, coverage, resolution, property record and event search tool on this server is free, unauthenticated and does not need an account, permanently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoA short name for this account, for your own reference on receipts. Optional.
quote_idNoIf you already hold a quote, pass it and the reply will name the exact funding call for it.
principalNoWho is behind this agent: the party whose money is being spent. Optional, stored as a CLAIM and never verified. It is not your software's name: 'Claude Desktop' is a client, not a principal.

TDQS

A4.9/5.0
Behavior5/5

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

Annotations are all false and offer no safety signals, so the description carries the full burden. It discloses the one-time return of the account key, that DFX stores only a digest and cannot show it again, that the account starts at $0, and that no argument can propose a balance. It also clearly states the mutating nature and the absence of idempotency expectations. No contradiction with annotations.

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 lengthy but every sentence earns its place: critical warnings (one-time key, zero balance, no balance arguments) are front-loaded, and the usage condition is stated in a separate, clear paragraph. The structure makes the essential information easy to parse.

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?

With no output schema and non-informative annotations, this description is remarkably complete. It covers what the tool does, why it exists, critical storage requirements, the zero-balance invariant, the inability to manipulate balances, and exactly when to use it versus alternatives. No significant gap remains for an agent deciding whether and how to call 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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema: it explains 'quote_id' in the context of a follow-up funding call, and clarifies 'principal' as the party whose money is spent, explicitly excluding software names like 'Claude Desktop.' Label is not expanded, but overall the description elevates parameter understanding.

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 a specific verb and resource: 'Creates an economic identity you control, with NO money in it.' It clearly distinguishes itself from siblings by emphasizing that this account starts at $0 and is required only for paid capabilities, while free sibling tools are unauthenticated and permanent.

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 'Call this only if you intend to buy a paid capability' and enumerates that every other discovery, coverage, resolution, property record, and event search tool is free and does not need an account. This gives an agent clear when-to-call and when-not-to-call guidance, exceeding typical alternative routing.

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

All DFX Real Estate Intelligence 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.1/5.0
Disambiguation5/5

Each tool targets a clearly distinct task: exact address resolution versus filter-based parcel search, subscription delta versus event search, coverage status versus natural-language routing, and the account lifecycle is split into open/fund/status. Even the closest pairs, changes_since and search_property_events, are explicitly disambiguated in their descriptions.

Naming Consistency3/5

The dominant pattern is verb_noun, e.g. resolve_address, search_parcels, get_property_record, but several tools break it: dfx_coverage, dfx_payment_status, debt_maturity_schedule, changes_since, and what_can_dfx_answer. These names are still readable and semantically clear, so the naming is mixed rather than chaotic.

Tool Count5/5

Twelve tools is well within the ideal range and each tool earns its place: discovery, coverage, resolution, search, records, event subscription, paid maturity schedules, and the account/payment lifecycle all have a distinct role. No tool feels redundant or ornamental.

Completeness4/5

The read-only real estate intelligence surface is well covered: coverage checks, address and organization resolution, property records, parcel search, event search, delta subscription, paid loan schedules, and account funding. The main gap is that resolve_organization returns entity IDs without an obvious downstream tool for organization detail, and there is no separate event detail endpoint, but agents can work around these.

Resources