Skip to main content
Glama

VetJobs.au - veterinary jobs in Australia

Listings changed since a timestamp

recent_changes

Incremental sync: every listing created or updated since the given ISO 8601 timestamp, newest first. Poll this instead of re-fetching the whole board — combine with the returned ids to keep a local copy current. Expired listings are never returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "updated_since": "<updated_since>"
    },
    "name": "recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
per_pageNo
first_partyNoRestrict to first-party (non-imported) listings.
updated_sinceYesISO 8601 date or datetime to sync from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 ordering (newest first), exclusion of expired listings, and the incremental-sync pattern. However, it does not cover pagination behavior, permissions/auth needs, rate limits, or response shape, which are important for a polling endpoint.

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?

Three compact sentences, front-loaded with the core concept (incremental sync) and the key behavioral constraint (expired listings excluded). Every sentence adds useful information.

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

Completeness3/5

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

The description covers purpose, ordering, and an important exclusion, but with no output schema and only partial parameter documentation, it omits pagination semantics and response details needed for a sync tool. It is adequate but incomplete for correct repeated invocation.

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

Parameters2/5

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

Schema coverage is only 50%, and the description mentions only the timestamp parameter, without adding format or meaning beyond what the schema says. It does not explain the pagination parameters (page, per_page) that are undocumented in the schema, nor does it clarify first_party behavior beyond the schema description.

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?

The description states a specific operation: return every listing created or updated since an ISO timestamp, newest first. It is clearly an incremental sync rather than a full board fetch. It does not differentiate itself from the named siblings (search_jobs, get_job, list_categories), so it falls short of a 5.

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?

It gives clear usage context: poll this instead of re-fetching the whole board, and use returned ids to maintain a local copy. It does not state when not to use it or name a specific alternative sibling, so it is not a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources