Skip to main content
Glama
Capital-W-Holdings

DFX Real Estate Intelligence

by Capital-W-Holdings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

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

open_dfx_account

Opens a free DFX account to establish a self-custodied economic identity, returning a one-time key for future access.

Instructions

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses important side effects: the key is returned once, only its digest is stored, it cannot be shown again, and the account starts at zero. It also clarifies that balance changes only occur through Stripe-confirmed payments, aligning with the readOnlyHint=false annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is somewhat repetitive with capitalized emphasis (e.g., 'NO money' and 'STARTS AT $0.00'), but each sentence adds meaningful operational detail. It could be tightened without losing crucial warnings.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers core behavior, side effects, and usage conditions well despite the lack of an output schema. It does not specify exact output format or error scenarios, but it gives enough context for an agent to use the tool safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters are described with added nuance beyond the schema. In particular, principal is clarified as a claim that is never verified and distinguished from the client software name, which prevents a common misuse.

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 creates an economic identity/account and explicitly notes it starts with no money. It distinguishes itself from sibling tools by emphasizing that free discovery tools do not need an account.

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?

It gives explicit when-to-use guidance: call only if intending to buy a paid capability, and states that all free tools work without an account. It also explains how quote_id affects the reply.

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

Deploy Server

Other Tools