Skip to main content
Glama

Follow a company

follow_company
Idempotent

Requires techjobs.vn sign-in. Follows a company for the signed-in user, so techjobs.vn notifies them when it posts new jobs. Following a company already followed changes nothing. Find the slug with search_companies; for new jobs in a role at any company use set_role_alert.

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": {
      "slug": "<slug>"
    },
    "name": "follow_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesCompany slug from search_companies or search_jobs, e.g. "grab".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes beyond the annotations by disclosing an auth prerequisite (sign-in required), the user-visible side effect (notification on new postings), and the repeat-call semantics in plain language. The idempotency statement reinforces the idempotentHint rather than merely restating it.

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?

Four short sentences with the prerequisite front-loaded, then purpose, then idempotency, then alternatives — an efficient ordering. Every sentence contributes a distinct fact; there is no filler despite the repeated product name.

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 one-parameter mutation with no output schema and rich annotations, the description covers the missing pieces an agent needs: auth requirement, side effect, idempotency, and sibling routing. Nothing material is left to inference.

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 slug field already documents its source and an example, so the schema carries the load. The description's "Find the slug with search_companies" largely duplicates the schema text, adding no new format or validation detail — baseline 3 is appropriate.

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?

Uses a specific verb and resource ("Follows a company for the signed-in user") and immediately states the consequence — notification on new job posts. It is clearly separable from neighbors like get_company (retrieve) and set_role_alert (role-based alerts at any company).

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?

Tells the agent how to obtain the required input (find the slug via search_companies) and routes the adjacent-but-different need to the correct alternative (set_role_alert for role-wide job alerts). It also states the no-op condition for an already-followed company, so the agent knows calling twice is safe.

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