Skip to main content
Glama

DomDom Jobs

List DomDom Jobs boards

list_boards
Read-onlyIdempotent

The DomDom Jobs boards and the types of work on each (the type values search_jobs takes), with open job counts from the nightly build and their URLs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world operation, so the description need not restate safety. Instead it adds genuinely new behavioral context: the counts come from a nightly build, which tells an agent the data may be up to a day stale. That freshness caveat is exactly the kind of information annotations cannot express. It stops short of describing the return structure, which matters somewhat since there is no output schema.

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?

It is a single sentence with no padding, and the key payload (boards, types, counts, URLs) is stated upfront. The nested parenthetical and the trailing 'and their URLs' make it slightly dense and back-loaded, but nothing is superfluous.

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 zero-parameter, read-only enumeration tool with no output schema, the essential facts are covered: what is listed, what each entry carries, where the counts come from, and how the output relates to search_jobs. The one gap is the shape of the returned data (whether it is an array of board objects), which an agent must guess. Given the tool's simplicity, this is close to complete.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to clarify at the input level; baseline is 4. The description does usefully explain what the implicit output contains (boards, types, counts, URLs), which compensates for the absent output schema at the parameter-adjacent level.

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 the specific resource (DomDom Jobs boards) and enumerates what each entry contains: work types, open job counts, and URLs. It is identifiable and distinct from search_jobs because it explicitly says it supplies the type values that search_jobs consumes. It loses a point only because it is a noun fragment with no verb, so the action (listing/retrieving) is inferred rather than stated.

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

Usage Guidelines3/5

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

The parenthetical '(the type values search_jobs takes)' implies a discover-then-search workflow, which is useful routing guidance. However, it never explicitly says when to call this versus search_jobs, nor does it state any exclusions or preconditions. Usage is implied rather than directed.

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