Skip to main content
Glama

Search companies hiring in Vietnam

search_companies
Read-onlyIdempotent

Find companies tracked by techjobs.vn by name, with their number of open jobs and referrers. Use to look up a company's slug, then get_company for its profile or search_jobs for its jobs.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage of `limit` results, starting at 1; up to page 3 without sign-in.
limitNoMaximum companies to return (default 10): up to 10 without sign-in, 50 when signed in.
queryNoPart of the company name or slug, e.g. "grab". Omit to list companies with the most open jobs.

Output Schema

NameRequiredDescriptionDefault
totalYes
noticeNo
companiesYes

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does, disclosing that results carry open-job counts and referrers. It stops short of mentioning the unauthenticated page/limit caps, though the schema carries those.

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 tight sentences: the capability and its return fields come first, the routing advice second. No filler, and the most decision-relevant information is front-loaded.

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?

For a read-only search with rich annotations, a fully described 3-parameter schema, and an output schema, the description supplies exactly the missing pieces: what the results contain and how this tool chains into get_company and search_jobs. Nothing an agent needs to call it correctly is absent.

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 page, limit, and query are already fully documented, including the omit-to-list-most-jobs behavior. The description only restates that matching is by name, and is actually slightly narrower than the schema, which also matches on slug — so it adds no meaning beyond the schema.

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?

The description names a specific verb and resource ('Find companies tracked by techjobs.vn by name') and adds scope detail ('with their number of open jobs and referrers') that separates it from generic listing tools. It also contrasts itself with get_company and search_jobs, so an agent can place it among siblings without opening any 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?

It states an explicit workflow: use this to look up a company's slug, then call get_company for the profile or search_jobs for its jobs. That is a when-to-use plus two named alternatives with their conditions, leaving nothing to inference.

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