Skip to main content
Glama

DFX Real Estate Intelligence

by io.github.Capital-W-Holdings
OverviewDiscussionsAdmin

Who occupies a property, or where a company operates

get_occupancy
Read-onlyIdempotent

Two directions from one call. A PROPERTY dfx_id returns the tenants observed at that building: tenant name and dfx_id, occupancy class, leased area, share of the property, and the lease expiration date where the source discloses one. A COMPANY dfx_id returns where that company is observed to operate. company with address (plus city and state) checks ONE claim: does DFX hold this company at this building. Every row carries its evidence tier and its freshness. Free. not_observed IS NOT VACANT. The published tenancy sources name only the largest tenant of a building, so most real occupiers are outside the disclosure entirely and an absent row is an absent disclosure, never a statement about the space. Accepts the canonical property and company dfx_ids carried by address and name resolution results and by event rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoMunicipality. The parcel key includes it, so an address without a city resolves poorly.
limitNoMax rows. A large building can disclose several tenants.
stateNoTwo-letter US state code.
dfx_idNoA property dfx_id (returns its tenants) or a company dfx_id (returns its locations). The direction is read from the object, not from a flag.
addressNoStreet address for the one-claim check. Used together with `company`.
companyNoCompany name, for the one-claim check. Used together with `address`; a company name alone is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"Street address for the one-claim check. Pass `company` with it."New value: +"Street address for the one-claim check. Used together with `company`."
    • changedInput schema / properties / company / description
      Previous value: -"Company name, for the one-claim check. Pass `address` with it."New value: +"Company name, for the one-claim check. Used together with `address`; a company name alone is refused."
    • changedInput schema / properties / dfx_id / description
      Previous value: -"A property dfx_id (returns its tenants) or a company dfx_id (returns its locations). The direction is read from the object, not from a flag you have to set."New value: +"A property dfx_id (returns its tenants) or a company dfx_id (returns its locations). The direction is read from the object, not from a flag."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/openWorld=false) by disclosing the critical epistemic caveat that 'not_observed IS NOT VACANT', that rows carry evidence tier and freshness, and that the tool is free. These are the exact behavioral traits an agent needs to avoid misinterpreting an empty result.

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?

Front-loads the two-direction mental model, then the per-direction returns, then the one-claim check, then the caveat. Dense but every sentence carries load, including the one-word 'Free.' cost signal.

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?

No output schema exists, and the description compensates by enumerating the returned fields (tenant name, dfx_id, occupancy class, leased area, share, lease expiration) plus evidence tier and freshness. With annotations covering safety, nothing an agent needs is missing.

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, but the description adds real meaning: direction is inferred from the object rather than a flag, address and company must be used together, and a company name alone is refused. It adds actionable semantics beyond the schema text.

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?

States a precise verb+resource pattern ('Two directions from one call') and enumerates exactly what each direction returns (tenant name, dfx_id, occupancy class, leased area, share, lease expiration). An agent can distinguish this from get_property_record or resolve_address without opening any schema.

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?

Clearly states when to use each mode: dfx_id for a property's tenants or a company's locations, and `company`+`address` for a single one-claim check ('company name alone is refused'). It gives strong in-tool routing but never names a sibling tool as the alternative when a different question is asked (e.g. get_property_record).

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources