Skip to main content
Glama

BuilderVet — NSW builder licence & risk history

by io.github.jackfieldman

search_builders

Read-only

Search Australian (currently NSW) builders, contractors and building companies by name; optionally filter by postcode. Returns matching entities with their licence status and a slug to pass to get_builder_risk / get_builder_timeline. Example: query='Acme Building' → '- Acme Building Pty Ltd (Current), 2099 → slug: acme-building-pty-ltd-1a2b'. Names are matched loosely, so try the trading name AND the legal (Pty Ltd) name if the first search misses. Query must be at least 2 characters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesBuilder or company name, e.g. 'Acme Building'
postcodeNoOptional NSW postcode filter, e.g. '2099'

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations indicate readOnlyHint=true; the description adds that search is loose, requires minimum 2 characters, and what the output contains (licence status, slug). No contradictions.

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?

Concise yet comprehensive: describes purpose, provides example, usage tips, and links to sibling tools. No unnecessary sentences.

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?

Despite no output schema, the description fully explains what is returned and how to use the output (slug) with other tools. Covers all 2 parameters adequately.

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% but description adds value by explaining query parameter usage (e.g., try different names) and postcode as an optional NSW filter, plus the minLength constraint.

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 searches for builders by name with optional postcode filtering, and distinguishes from sibling tools by mentioning it returns slugs for get_builder_risk and get_builder_timeline.

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?

Provides explicit guidance on when to use (searching builders), includes an example, advises trying both trading and legal names, and explains that the output slug feeds into related tools.

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

All BuilderVet — NSW builder licence & risk history 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

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct role: search_builders finds entities, get_builder_risk returns a consolidated factual profile, and get_builder_timeline returns dated events. There is no meaningful overlap between them.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: search_builders, get_builder_risk, get_builder_timeline. The naming clearly signals both the action and the resource.

Tool Count5/5

Three tools is a well-scoped size for a focused read-only registry lookup server. Each tool serves a necessary step in the workflow: search, profile, and timeline.

Completeness5/5

The server covers the full intended workflow for builder licence and risk history lookup: find a builder, retrieve their factual risk profile, and inspect their dated event timeline. No obvious dead ends or missing core operations are apparent.

Resources