Skip to main content
Glama
jobinja-mcp

jobinja-mcp

by sepehr071

Job market counts

jj_market
Read-onlyIdempotent

Count open Jobinja job ads by category, province, industry, and top skill; when a province is given, list its cities for city filtering.

Instructions

Count open Jobinja ads now per category, province, industry and top skill.

With province, also exact city names for the city filter.

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

Input Schema

NameRequiredDescriptionDefault
provinceNoAlso list this province's cities, e.g. اصفهان.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • removedInput schema / properties / province / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / province / description
      Previous value: -"Province name to also list its cities with ad counts, e.g. اصفهان."New value: +"Also list this province's cities, e.g. اصفهان."
    • addedInput schema / properties / province / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds that counts are a 'now' snapshot of open ads and that province yields city names, but says nothing about count accuracy, truncation of 'top skill', or caching/staleness.

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, front-loaded with the verb and dimensions, with the only conditional behavior (province) following immediately. No filler or redundant phrasing.

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 low-complexity read-only aggregate tool with full schema coverage and complete annotations, the description covers scope, dimensions and the province side effect. The main gap is that the return shape (e.g., how many top skills, per-dimension structure) is unspecified and no output schema exists to compensate.

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 single parameter's schema description already explains that it lists the province's cities. The description's province clause largely restates the schema without adding format or example detail, so the baseline 3 applies.

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 a specific verb ('Count') and resource ('open Jobinja ads') plus the exact breakdown dimensions (category, province, industry, top skill). That clearly distinguishes it from the listing-oriented siblings like jj_search_jobs and jj_company_jobs, though no sibling is named explicitly.

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?

Usage is implied by the word 'Count' versus the search siblings that return ads, and the 'with province' clause hints at when to pass that parameter. There is no explicit when-to-use/when-not guidance or reference to jj_filters or jj_search_jobs as alternatives.

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