Skip to main content
Glama

DomDom Jobs

One employer on DomDom Jobs

get_company
Read-onlyIdempotent

One employer's open jobs on DomDom Jobs: how many per board, posted pay, its company pages, open jobs by day for the last 30 days, and its newest jobs.

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": {
      "company": "<company>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoJobs to return, default 10.
companyYesEmployer name or slug, e.g. "Mercor", "Hinge Health".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. With no output schema, the description's enumeration of returned sections (pay, boards, 30-day series, newest jobs) is genuinely useful behavioral context. It still omits what happens when the company name does not resolve and whether the multi-section response is truncated by limit.

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 scope and then lists the payload sections. Every clause maps to real returned data; it is dense but not padded.

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?

For a two-parameter read with no output schema, describing the returned sections is the right instinct and covers most of what an agent needs. However, the interaction between limit and the several data blocks, and failure behavior for an unknown employer, remain unaddressed.

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%, and the schema already explains both the company name/slug and the limit with its default of 10 and maximum of 25. The description adds no meaning beyond that, and leaves it ambiguous whether limit constrains the newest-jobs section, the per-board counts, or both.

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 identifies a specific resource (one employer on DomDom Jobs) and enumerates the distinct data it returns: jobs per board, posted pay, company pages, a 30-day posting series, and newest jobs. That is far more than a restatement of the name. It stops short of a 5 because it reads as a list of payload sections rather than stating the action, and it never distinguishes itself from siblings like search_jobs or pay_snapshot.

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?

Nothing states when to reach for this tool rather than search_jobs, list_boards, or pay_snapshot. The phrase 'One employer's' implies you need a specific company in hand, but there is no explicit precondition, no exclusion, and no routing to alternatives.

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