Skip to main content
Glama

DomDom Jobs

DomDom Jobs pay by type of work

pay_snapshot
Read-onlyIdempotent

What jobs on one DomDom Jobs board pay, overall and per type of work: the pay sentence the board prints, the range most posted rates fall in (hourly and yearly kept apart) and how many jobs post pay. Pay as employers post it, estimates left out.

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

Input Schema

NameRequiredDescriptionDefault
typeNoType of work: a hub key on the chosen board, e.g. nurses (healthcare), lawyers (legal), weekends (moonlight), operator (robots). See list_boards.
boardNohome searches every board; the others are robots, healthcare, ux, moonlight, veterans and legal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false already supplied, the description adds real value: it discloses that pay is as employers post it, that estimates are excluded, that hourly and yearly figures are kept apart, and that it reports how many jobs post pay. That directly warns the agent about mixed units and partial coverage — the main pitfalls here — though it says nothing about pagination or empty-result behavior.

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?

A single front-loaded sentence that opens with the core question the tool answers and then enumerates the three return components. It is dense with parentheticals but every clause carries information; nothing is padding.

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?

For a two-parameter, read-only, closed-world tool with no output schema and full schema coverage, the description covers what the agent most needs: what is returned, that units are split, and that estimates are excluded. Only cross-tool routing and edge-case behavior (no pay posted, invalid type key) are left unstated.

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 100%, with both the type key and the board enum fully documented in the schema, including the note that 'home' searches every board. The description adds only the framing that results are overall plus per type of work, which implies type is an optional narrowing rather than a requirement; it does not add new syntax or format detail beyond the schema.

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 names a specific resource and scope: pay data for jobs on a single DomDom Jobs board, decomposed into the printed pay sentence, the typical posted range, and the count of jobs posting pay. It is clearly distinguishable from search_jobs or list_boards, though it never names a sibling to contrast against, which keeps it 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. An agent can infer this is the tool for pay questions, but nothing tells it whether to prefer search_jobs first or how this relates to list_boards for discovering valid board/type keys.

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