Skip to main content
Glama
Sign In
100Hires MCP Server

100Hires MCP Server

Official
by 100Hires
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hires_list_boards

Discover available publishing boards with essential metadata to simplify distribution setup and select the right board for your job posts.

Instructions

List available publishing boards with metadata. Use for distribution setup and board selection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool lists boards with metadata, but does not disclose whether it is read-only, whether special permissions are needed, or what scope of data is returned. This is a significant transparency gap.

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?

The description is extremely concise, with two short sentences. The first sentence front-loads the purpose, and the second adds usage context. There is zero redundancy or wasted words.

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 list tool with no output schema, the description is somewhat complete: it covers purpose and usage. However, it fails to specify what 'metadata' is returned, and it does not clarify how this tool relates to similar ones like hires_list_job_boards. Thus, there are clear gaps that could confuse an agent.

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 input schema has zero parameters, so the baseline for this dimension is 4. The description adds no parameter details, but none are needed; it appropriately avoids commenting on nonexistent parameters.

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 clearly identifies the tool's function: 'List available publishing boards with metadata.' It specifies a resource (publishing boards) and includes metadata, which differentiates it from generic list tools. However, it does not explicitly distinguish itself from similar siblings like hires_list_job_boards, so it falls just short of a perfect score.

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?

The description provides explicit usage context: 'Use for distribution setup and board selection.' This tells the agent when to employ the tool. However, it does not mention exclusions or alternative tools, so it lacks full 'when not to use' guidance.

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