Skip to main content
Glama

Search tech roles

search_roles
Read-onlyIdempotent

Search open tech roles in Egypt, Saudi Arabia, the UAE and remote roles open to people there, newest first. Words match the title, company, place, stack and level, with common other names (frontend finds front end, flutter finds mobile roles). Every filter is optional. One company's roles and profile come from company_roles, in a card of their own.

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_roles"
  }
}

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
limitNoHow many roles (default 20)
offsetNoSkip this many, for the next page (next_offset)
companyNoCompany ids (as in company_id)
countryNoeg Egypt, sa Saudi Arabia, ae UAE, remote: remote roles open to people in the region
posted_within_daysNoPosted in the last 7, 30 or 90 days (default 90)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior the annotations cannot convey: relevance/synonym expansion (frontend finds front end, flutter finds mobile roles), which fields the words match against, and the newest-first sort order.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with scope and ordering, no filler. The trailing clause 'in a card of their own' is slightly vague phrasing, but it costs little and the rest is dense and purposeful.

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?

For an 11-parameter, all-optional search tool with full schema coverage, no output schema, and rich annotations, the definition covers scope, ordering, matching behavior and sibling routing. Pagination behavior is only hinted at via the schema's next_offset mention, which is a minor gap rather than an omission an agent would stumble on.

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% and the enum values are already documented, so the schema does the heavy lifting. The description adds only general matching semantics for the query words and the regional scope, without clarifying ambiguous parameters such as how company ids relate to company_roles or how pay=true interacts with unlisted salaries.

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 (search open tech roles) plus the exact geographic scope (Egypt, Saudi Arabia, UAE, remote-for-the-region) and the ordering (newest first). It also distinguishes itself from the sibling company_roles by noting that a single company's roles and profile come from that tool instead.

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

Usage Guidelines4/5

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

Explicitly says every filter is optional, which tells the agent a bare call is valid, and routes single-company lookups to company_roles. It does not contrast with get_role or create_alert, but the routing it does give is concrete and correct.

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