Skip to main content
Glama

Attom

by io.github.pipeworx-io

Attom School Search

attom_school_search
Read-onlyIdempotent

"Schools near [address]" / "what school district is [house] in" / "best schools in [area]" / "public schools around [coords]" — find K-12 schools near a US location by lat/lng radius. Returns school name, type (public/private), grade levels, distance, and performance rankings. Use for relocation / family-housing questions paired with property search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
radiusNoSearch radius in miles (default 5, max 20)
_apiKeyYesATTOM API key
latitudeYesLatitude of the search center
longitudeYesLongitude of the search center

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already convey readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, which are not contradicted. The description adds that the tool returns school name, type, grade levels, distance, and performance rankings, which is useful behavioral context beyond the 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 a single, well-structured paragraph with front-loaded example queries. Every sentence is meaningful and there is no fluff. At about 50 words, it is appropriately concise.

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 tool has an output schema (indicated true), the description does not need to detail return values. It covers the core purpose, example use cases, and key return fields (school name, type, grade levels, distance, performance rankings). This is complete for a search 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%, so the baseline is 3. The description does not add extra meaning beyond what the schema provides (radius default and max, lat/lng required). It mentions 'by lat/lng radius' but that is already implicit.

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 uses specific verbs ('find', 'returns') and clearly states the resource ('K-12 schools near a US location by lat/lng radius'). It includes concrete example queries (e.g., 'Schools near [address]'), which distinguishes it from sibling tools like property search or assessment.

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?

The description explicitly states the use case: 'Use for relocation / family-housing questions paired with property search.' This provides clear context. However, it does not explicitly mention when not to use this tool or name alternatives, though the sibling list lacks other school tools, making the guidance sufficient.

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

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

A3.7/5.0
Disambiguation2/5

Several tools overlap heavily: ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, and ask_pipeworx_grounded shares the same router. The universal ask_pipeworx router also subsumes many domain-specific tools (attom_*, entity_profile, etc.), making it unclear when to use the specialist tools versus the catch-all.

Naming Consistency3/5

All names are snake_case and mostly descriptive, but conventions vary: ask_* and attom_* prefixes coexist with bare verbs (remember, forget, subscribe), noun phrases (entity_profile, polymarket_edges), and adjective-prefixed names (recent_alerts, recent_changes). The pattern is readable but not uniform.

Tool Count2/5

39 tools is well over the 25+ threshold for a heavy surface, especially for a server named 'Attom' that also includes memory, subscriptions, feedback, npm scanning, and AI-visibility tools beyond real estate. Many tools could be consolidated (e.g., the three ask_pipeworx variants, the six polymarket tools).

Completeness4/5

The real estate domain is well covered (search, detail, AVM, rental AVM, sales history, trends, assessment, schools), and the broader data platform includes discovery, grounded answers, entity profiles, comparisons, claim validation, subscriptions, and memory. Minor gaps exist only around edge features like OAuth-gated subscription persistence.

Resources