Skip to main content
Glama
irantalent-mcp

irantalent-mcp

by sepehr071

Company reviews

it_company_reviews
Read-onlyIdempotent

Retrieve anonymous employee reviews for a company—ratings, pros, cons, and job titles—to assess what it is like to work there.

Instructions

Read anonymous employee reviews of a company on IranTalent: ratings, pros, cons, reviewer's job title.

Use for "what is it like to work at X". Ratings are 1-5. Only reviews with written text are listed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_id": "<company_id>"
    },
    "name": "it_company_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based; 30 per page.
sortNoOrder.newest
company_idYesCompany UUID from it_search_jobs, it_companies or it_top_companies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.0
    • changedInput schema / properties / company_id / description
      Previous value: -"Company id (a UUID) from it_search_jobs (company.id), it_companies or it_top_companies."New value: +"Company UUID from it_search_jobs, it_companies or it_top_companies."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 1-based. 30 results per page."New value: +"1-based; 30 per page."
    • changedInput schema / properties / sort / description
      Previous value: -"Newest first (default) or most helpful first."New value: +"Order."
  2. First observedv0.1.1

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=true, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the 1-5 rating scale and the significant coverage caveat that only reviews with written text are listed. It does not mention pagination limits, though the schema does.

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 short sentences with the resource and payload first, the usage trigger second, and the two hard constraints (scale, written-text-only) at the end. Every sentence carries information an agent needs; nothing is padding.

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?

With no output schema, the description usefully names the returned fields and flags the written-text-only filter, which prevents an agent from assuming full review coverage. Pagination size and ordering are left entirely to the schema, which is a minor gap rather than a blocking one.

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%, with page (30 per page), sort enum, and company_id source documented inline, so the schema does the heavy lifting and baseline 3 applies. The description adds nothing about page or sort behavior, and it does not restate where to obtain company_id.

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?

States a specific verb and resource ('Read anonymous employee reviews of a company') and enumerates the returned fields (ratings, pros, cons, reviewer's job title), which is far more than a restatement of the name. It does not explicitly distinguish itself from siblings like it_salary_reports or it_job_market, so an agent must infer the boundary between reviews and salary data.

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?

Provides a clear intent trigger ("what is it like to work at X"), which implies when to reach for it. However, it names no alternatives and gives no exclusions — it never says to use it_salary_reports for compensation questions or it_company for company facts, so routing among the it_* review/company cluster is left to inference.

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