Skip to main content
Glama

Вакансии в ИБ и ИТ

cisoclub_jobs
Read-onlyIdempotent

Открытые вакансии в информационной безопасности и ИТ на cisoclub.ru, от новых к старым: должность, компания, город, зарплата, опыт, график и тип занятости.

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

Input Schema

NameRequiredDescriptionDefault
cityNoГород, как на сайте: Москва, Санкт-Петербург
pageNoНомер страницы выдачи, от 1 до 5
limitNoСколько материалов вернуть, от 1 до 20
queryNoСлова для поиска: должность, навыки, компания; до 8 слов
remoteNotrue — только удалённая работа

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / results / items / properties / course / properties / code
      Added value: +{
      +  "description": "Код курса в центре обучения, если указан",
      +  "type": "string"
      +}
    • changedOutput schema / properties / results / items / properties / event / description
      Previous value: -"У мероприятия: когда, где, формат и регистрация"New value: +"У мероприятия: когда, где и регистрация"
    • removedOutput schema / properties / results / items / properties / event / properties / format
      Removed value: -{
      -  "description": "online, offline или hybrid",
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
  2. Changed8 schema fields changed
    • addedOutput schema / properties / results / items / properties / audiences
      Added value: +{
      +  "description": "Для кого материал",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / results / items / properties / course / properties / track
      Added value: +{
      +  "description": "Трек обучения, если указан",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / event / properties / age
      Added value: +{
      +  "description": "Возрастная группа, если указана",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / industries
      Added value: +{
      +  "description": "Отрасли",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / results / items / properties / job / properties / address
      Added value: +{
      +  "description": "Адрес офиса, как на странице вакансии",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / job / properties / metro
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / tags
      Added value: +{
      +  "description": "Метки материала",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / results / items / properties / topics
      Added value: +{
      +  "description": "Темы",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds useful behavior beyond that by disclosing chronological ordering and the vacancy fields shown, while the output schema covers return structure.

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 definition is a single, front-loaded sentence with no filler. It states source, domain, ordering, and displayed fields efficiently.

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?

Given a simple read-only listing tool with full schema descriptions, an output schema, and clear annotations, the description is nearly complete. The only meaningful gap is the absence of guidance on how this relates to the generic cisoclub_search tool.

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 100%, and the schema precisely documents city, query, page, limit, and remote with ranges and defaults. The description does not add filter syntax or interpretation beyond the schema, so baseline 3 is appropriate.

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 (open information security and IT vacancies on cisoclub.ru) and states the ordering (newest first), which distinguishes it from sibling tools covering events, news, vulnerabilities, and products. It lacks a direct action verb, but the listing purpose is unambiguous.

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?

Use is implied: an agent can infer this tool is for browsing job vacancies, and the ordering and displayed fields clarify the intended result. However, it gives no explicit guidance on when to use this tool instead of the generic cisoclub_search sibling, nor any when-not conditions.

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