Skip to main content
Glama

Get alerts for new roles

create_alert

Sets up free Telegram alerts for new roles matching a search; it takes the same filters as search_roles. It returns a link: the person taps it and presses Start in Telegram, and nothing is sent until they do. It also returns email_page, a page where the person can sign up for email alerts with their own address.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch words, for example "backend golang" or "data analyst"
payNoOnly roles that list their pay
cityNoCities (eastern is Dammam and Khobar)
typeNoJob type: eng engineering, data data and AI, infra infrastructure and IT, security, product product and design
fieldNoNarrower field inside a job type, for example backend, mobile, devops, ml
levelNoSeniority
companyNoCompany ids (as in company_id)
countryNoeg Egypt, sa Saudi Arabia, ae UAE, remote: remote roles open to people in the region

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true) the description discloses the important non-obvious behavior: a link is returned, the person must tap it and press Start, and nothing is sent until they do, plus a second email_page output. It does not address idempotency, which matters given idempotentHint=false and no required parameters — repeated calls may create duplicate alerts.

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 compact sentences: what it does, how activation works, and what else is returned. The critical constraint ('nothing is sent until they do') is stated inline with the link behavior, and there is no filler.

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 side-effecting, zero-required-param creation tool with no output schema, the description covers the action, the two returned artifacts (link and email_page), and the human confirmation gate. The only unaddressed detail is duplicate-alert behavior on repeat calls, which is minor relative to what is covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns the extra point by clarifying that all 8 parameters are identical search filters to search_roles rather than alert configuration, which is genuine meaning the schema alone does not convey.

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 gives a specific verb and resource ('Sets up free Telegram alerts for new roles matching a search') plus the scope qualifier that it takes the same filters as search_roles, which separates it from the read-only siblings search_roles/get_role/company_roles. An agent can tell what it produces without opening the schema.

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?

Referencing search_roles establishes that this is the 'turn a search into an alert' path, which implies when to use it, but there is no explicit when-to-use/when-not statement or named alternative for someone who just wants results once. Usage is inferred rather than stated.

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