Skip to main content
Glama
Sign In

FactLot

by io.github.9mp96ygnbk-alt
OverviewDiscussionsAdmin

Resolve an external ID

registry_resolve_external
Read-onlyIdempotent

Find the FactLot URN for an ID from another system, e.g. system "sdat_account" (a Maryland SDAT account number) or, where Texas is hosted, "hcad_account" (a Harris CAD account number). Requires a FactLot Registry (public-record facts about commercial property, each cited to the source file and record).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "system": "<system>",
      "external_id": "<external_id>"
    },
    "name": "registry_resolve_external"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemYesCrosswalk system name, e.g. "sdat_account" (Maryland), or "hcad_account" where Texas is hosted.
external_idYesThe ID in that system.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / system / description
      Previous value: -"Crosswalk system name, e.g. \"sdat_account\" (Maryland), or \"tx-harris-cad-account\" where Texas is hosted."New value: +"Crosswalk system name, e.g. \"sdat_account\" (Maryland), or \"hcad_account\" where Texas is hosted."
  2. Changed1 schema field changed
    • changedInput schema / properties / system / description
      Previous value: -"Crosswalk system name, e.g. \"tx-harris-cad-account\"."New value: +"Crosswalk system name, e.g. \"sdat_account\" (Maryland), or \"tx-harris-cad-account\" where Texas is hosted."
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds the prerequisite of a FactLot Registry and briefly explains what the registry contains, but it does not describe not-found behavior or other operational edge cases.

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 front-loaded with the core action and stays to two sentences. The parenthetical examples and registry prerequisite are useful context rather than unnecessary padding.

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?

For a simple two-parameter lookup with rich annotations, the description covers purpose, example system values, and the FactLot Registry prerequisite. It does not explicitly state what happens when no match is found, but it is otherwise complete enough to invoke the tool.

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?

Schema description coverage is 100%, and the schema already documents both parameters with the same system examples and the meaning of external_id. The description repeats those examples without adding new format, validation, or lookup semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and result: "Find the FactLot URN for an ID from another system." It gives concrete system examples, but it does not explicitly distinguish this from sibling tools such as registry_resolve_parcel.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: call this when you have an external system ID and need the corresponding FactLot URN. The prerequisite "Requires a FactLot Registry" is stated, but there is no explicit when-not guidance or named alternative tool.

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

All FactLot 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