H1R3: Australian job board for bots

search_seekers

Search searchable seekers (ABN-verified employer key). Each result has verification_level (Basic verified | ID verified). Filters: id_verified_only, min_level (basic|phone|id), verified_task (code), verified_cert (type), verified_skill (badge), min_score, min_identity, min_skills, min_references (0-100).

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": "search_seekers"
  }
}

Input Schema

Name	Required	Description	Default
`skills`	No
`postcode`	No
`min_level`	No
`min_score`	No
`min_skills`	No
`work_rights`	No
`min_identity`	No
`verified_cert`	No
`verified_task`	No
`min_references`	No
`verified_skill`	No
`id_verified_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

addedInput schema / properties / id_verified_only
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / min_level

Added value: +{
+  "enum": [
+    "basic",
+    "phone",
+    "id"
+  ],
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the result shape ('Each result has verification_level (Basic verified | ID verified)') and the range of min_references (0-100), which is real behavioral value. It says nothing about pagination, result caps, privacy constraints, or permissions, which is a notable gap for a people-search tool.

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?

Front-loaded with purpose, then a compact filter list; little wasted text. The filter enumeration reads as a run-on sentence and would benefit from structure, but it is appropriately sized for a 12-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter search with no annotations and no output schema, the description is too thin: three parameters are unexplained, and pagination/result-size behavior and the caller's authorization model are absent. The one genuinely helpful addition, the verification_level result field, does not offset these gaps.

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 coverage is 0% across 12 parameters, so the description must compensate, and it does partially: it names nine filters and clarifies min_level's enum values and min_references' 0-100 range, matching the schema enum. However, skills, postcode, and work_rights are undocumented anywhere, and the 'code/type/badge' hints for verified_* are cryptic.

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 (Search) and resource (seekers), and adds the scope qualifier 'ABN-verified employer key' plus the fact that results carry verification_level. 'Search searchable seekers' is mildly tautological, and it never explicitly distinguishes itself from sibling search_jobs, but the employer-facing seeker search is clear enough to act on.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus search_jobs or other list_* siblings, and no prerequisites beyond the parenthetical 'ABN-verified employer key'. The enumerated filters imply the use case but leave the agent to infer the calling context entirely.

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

All H1R3: Australian job board for bots tools Inspect

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

Need Help?