Skip to main content
Glama
job-board-mcp

job-board-mcp

by adeolaoj

list_companies

Lists the companies this job-board server searches and the applicant tracking system each uses, so you can use exact names in job searches and job lookups.

Instructions

List the companies this server searches and which applicant tracking system each uses.

Use these exact names in search_jobs's `companies` filter and in get_job.

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_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the disclosure burden, and it does state what the call yields: the server's company set plus each company's ATS. It does not mention that the listing is unfiltered/unpaginated or whether the set is static versus dynamically discovered, which are the only behavioral unknowns left for a zero-parameter read tool whose output schema documents the return shape.

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?

Two short sentences, with the core purpose front-loaded and the actionable instruction (exact names for two named sibling tools) immediately after. Every clause earns its place; nothing is redundant with the schema or annotations.

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 trivial zero-argument enumeration tool with an output schema and no annotations, the description covers what it returns and how to consume the result. The only meaningful omission is guidance on how often the list can change or whether results are cached, which is minor but not zero for an agent planning call sequencing.

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 no parameter meaning to add and the baseline of 4 applies. The description still contributes by clarifying what the returned names are for, which is the closest analogue to parameter semantics here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('List') and resource ('the companies this server searches') and adds the payload detail that each entry carries an applicant tracking system identifier. An agent can immediately tell this apart from search_jobs and get_job, which are the two tools it explicitly feeds.

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?

Gives explicit downstream routing: the returned names are the exact values to pass in search_jobs's `companies` filter and in get_job, which is precisely the when-to-use context an agent needs. It stops short of saying when NOT to call it (e.g. that it takes no filter and should not be polled before every query), so it is strong but not complete.

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

Deploy Server

Other Tools