Skip to main content
Glama

BirJob

Find employers on BirJob

list_companies
Read-onlyIdempotent

Find employers on BirJob by name, with how many open jobs each has and the URL of its birjob.com company page. Use this when the user names or asks about an employer (şirkət, company, компания), or wants the biggest hirers: without a query it lists the employers with the most open jobs in Azerbaijan. Do not use for the jobs themselves: pass the company's url to search_jobs as company.

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
pageNoResult page, 1 to 20 (default 1), 10 results a page. Past page 20, send the user to search_url.
queryNoPart of the company name: "Kapital", "PASHA", "Azercell", "SOCAR". Leave out for the employers with the most open jobs in Azerbaijan.

Output Schema

NameRequiredDescriptionDefault
pageYes
pagesYes
queryYes
totalYes
companiesYes
next_pageYes
companies_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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 behavior the annotations cannot: that each result carries an open-job count and a company-page URL, and that omitting the query falls back to a most-open-jobs ranking rather than returning nothing. It does not discuss pagination or result caps, though the schema covers the page bound.

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?

Three sentences, front-loaded with purpose before usage and exclusions. Every clause earns its place: the output fields, the trigger phrases, the default behavior, and the negative case each carry distinct information with no repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (2 optional params) and an output schema exists, so return values need no explanation in prose. Combined with annotations covering safety and the description covering default behavior and sibling routing, an agent has everything needed to invoke this correctly.

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%, so both parameters are already documented in the schema, including the exact guidance that omitting query yields the top hirers. The description reinforces the name-matching semantics and the URL-to-search_jobs handoff but adds no new syntax or format detail beyond the structured fields, so the baseline of 3 applies.

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 and resource ("Find employers on BirJob by name") and immediately scopes the output: open-job counts plus the birjob.com company-page URL. It also explicitly distinguishes itself from search_jobs, so an agent can route between employer lookup and job lookup without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use triggers, including the multilingual surface forms (şirkət, company, компания) and the intent "wants the biggest hirers." It also documents the no-query default and states the exclusion ("Do not use for the jobs themselves") with a concrete handoff: pass the company's url to search_jobs as company.

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