Skip to main content
Glama
businessapi-mcp

businessapi-mcp

by JoeFu

Create Ppsr Search

create_ppsr_search

Create a PPSR search using ABN, ACN, VIN, serial number, registration number, organisation name, or individual grantor details, then poll the request ID until completed or failed.

Instructions

Create a PPSR (Personal Property Securities Register) search. LIVE cost: $6.00 per search.

Provide exactly ONE identifier set:

  • abn | acn | arbn | arsn -> grantor search by number (certificate yes)

  • vin -> vehicle serial search + NEVDIS vehicle data

  • serial_number + serial_number_type -> non-VIN serial search (ChassisNumber | HIN | OfficialNumber)

  • registration_number -> look up one PPSR registration (no certificate)

  • organisation_name -> grantor search by organisation name

  • family_name + given_names + date_of_birth (YYYY-MM-DD) + authorised_purpose=True -> individual grantor search; the user must confirm they have an authorised purpose under the PPS Act before you set it to True.

Returns {requestId, status: "new"}. Then poll get_ppsr_search(request_id) until status is "completed" or "failed".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_ppsr_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
abnNo
acnNo
vinNo
arbnNo
arsnNo
family_nameNo
given_namesNo
date_of_birthNo
serial_numberNo
organisation_nameNo
authorised_purposeNo
serial_number_typeNo
registration_numberNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, but the description adds what the annotations cannot: a real monetary cost ($6.00 per LIVE search), the asynchronous create-then-poll lifecycle, the exact return envelope {requestId, status:"new"}, and the legal prerequisite that the user must confirm an authorised purpose under the PPS Act before authorised_purpose is set to True. That is substantive behavior beyond structured fields, with no contradiction of the declared write/non-idempotent profile.

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?

Purpose and cost are front-loaded in the first two lines, the identifier matrix is presented as an aligned bullet list that mirrors the input space, and the lifecycle note closes the description. No sentence is redundant with the schema, and the density is appropriate for a 13-parameter tool.

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?

For a costly, asynchronous, multi-mode search tool, the definition covers mode selection, cost, return shape, and the poll-to-completion path. An output schema exists, yet the description still gives the minimal success envelope, which is the one thing an agent needs before deciding to poll.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 13 parameters, so the description carries the full burden and does: it groups parameters into exclusive sets, supplies the missing enum values for serial_number_type (ChassisNumber | HIN | OfficialNumber), specifies the date_of_birth format (YYYY-MM-DD), and explains the semantic meaning of authorised_purpose=True. This meaningfully exceeds what the bare typed schema conveys.

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 states a specific verb and resource ("Create a PPSR ... search"), names the register it queries, and immediately distinguishes the six mutually exclusive identifier paths (abn/acn/arbn/arsn, vin, serial_number+type, registration_number, organisation_name, name+DOB). An agent can tell exactly which mode of this tool applies without opening the schema.

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?

It gives explicit routing rules: "Provide exactly ONE identifier set" followed by a mapping of identifier combination to search behavior, including the negative case that registration_number returns no certificate and that VIN yields NEVDIS data. It also names the required follow-up sibling, get_ppsr_search(request_id), with the termination condition (status "completed" or "failed").

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