readback

search_catalog

Read-onlyIdempotent

Find where a number lives before writing SQL. Searches warehouse tables, columns, metrics and manifest values, expanding synonyms and ranking hits by a lexical index.

Instructions

Search the catalog of the three warehouses for tables, columns, metrics and published manifest values, ranked by a lexical index after the query is expanded through the synonym table (house price finds value_anchored). Returns the expanded query and up to k hits (at most 20), each with its unit and one definition sentence. Pass kind to search one kind only (definition finds the entries of each build's definitions document). Use it to find where a number lives before writing SQL.

Input Schema

Name	Required	Description	Default
`k`	No
`kind`	No
`query`	Yes
`warehouse`	No

Output Schema

Name	Required	Default
`hits`	Yes
`query`	Yes
`expanded`	Yes
`statement`	No	Answers are drawn from the published tables of three portfolio builds by Ajay Mekala: doorstep (public housing data from FHFA, the Census Bureau, HUD, the CFPB and Freddie Mac), turnaround (public flight data from the Bureau of Transportation Statistics, the FAA and OurAirports, with weather from Open-Meteo under CC BY 4.0) and ledger (a fictional bank, Harborline, with public HMDA, CFPB, FDIC and macro series). No person appears in any table, and questions are redacted before a model sees them. Every number is read back to the warehouse before it is shown. This is a portfolio demonstration, not financial, travel or lending advice.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 24, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: lexical ranking, synonym-table query expansion with an example, return of the expanded query, capped hits (at most 20), per-hit unit and definition sentence, and kind-specific behavior for definitions. Annotations already confirm it is read-only, idempotent, non-destructive, and closed-world; the description adds rich operational 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?

Front-loads the main action immediately and remains dense but purposeful. The synonym example and kind clarification earn their place, and there is no filler.

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?

Given the output schema and annotations, the description covers the core search semantics, ranking, result shape, and kind filtering well. The main remaining gap is that the warehouse parameter is not explained despite the low schema description coverage.

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?

With 0% schema description coverage, the description must carry parameter meaning. It explains query expansion, k's maximum of 20, and kind's one-kind-only behavior, including the definition kind, but it does not explain the warehouse parameter or its allowed values beyond implying the three warehouses exist.

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?

States a specific verb and resource: search the catalog of the three warehouses for tables, columns, metrics, and manifest values. The purpose is clear, but sibling differentiation is only implicit through the 'before writing SQL' context; no sibling tool is named as an alternative.

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?

Gives a clear usage context: use it to find where a number lives before writing SQL, and notes that passing kind restricts the search to one kind. It does not state when not to use it or explicitly name alternatives such as lookup or describe.

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

Deploy Server