Skip to main content
Glama

Jobs board

jobs_board
Read-onlyIdempotent

Open reviewed simple jobs, or an honest empty board while none are published. Optional province, town, kind, and remote_ok. Read only. Does not take an order or a payment.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
townNo
provinceNo
remote_okNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context on top: only *reviewed* jobs appear, and an empty result set is expected rather than an error, which tells the agent how to interpret a blank response. It also clarifies the tool is non-transactional.

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?

Short and front-loaded: the resource and its empty-state behavior come first, then the optional filters, then the read-only/non-transactional caveat. The phrase 'an honest empty board' is colorful but costs little; nearly every clause carries information.

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?

With no output schema and no documented response shape, the agent still does not know what fields each job carries, whether results are sorted or paginated, or how filters combine. For a pure listing tool the definition is workable, but it stops short of fully describing the result the agent will have to act on.

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 description coverage is 0%, so the description must carry parameter meaning. It names all four filters and marks them optional, but adds nothing about what the kind/province enums mean or how remote_ok interacts with town/province filtering. Naming without semantics leaves the schema's bare enums unexplained.

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 states a concrete resource and scope: reviewed 'simple jobs' listings, with an explicit note that an empty result is a legitimate outcome. It is distinguishable from siblings like job_draft_check or local_offer, though it never names a sibling, so the differentiation is implicit 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?

Browsing is implied by 'open ... board', and the closing clause 'Does not take an order or a payment' functions as a useful exclusion steering agents away from transactional tools. However, there is no explicit when-to-use sentence and no named alternative for drafting or checking a job.

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