Skip to main content
Glama

AIML Rounds

AI/ML jobs in India

jobs
Read-only

AI/ML job postings in India from the last 7 days (100+ companies, refreshed daily), newest first, with direct apply links to the company's careers page. Filter by keywords, company, city or years of experience.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoWords in the job title, e.g. 'machine learning engineer', 'GenAI', 'data scientist'
companyNo
locationNoCity, e.g. 'Bengaluru', 'Hyderabad', 'Remote'. Old names like 'Bangalore' or 'Gurgaon' also work
experienceNo'0-2', '2-5', '5-8', '8+' or a number of years

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: dataset size ('100+ companies'), refresh cadence ('refreshed daily'), recency window ('last 7 days'), ordering, and that results carry direct careers-page apply links.

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?

A single dense sentence that front-loads the resource and scope before the filter list; nothing is wasted. It is somewhat run-on with stacked parentheticals, which slightly slows parsing but adds useful facts.

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 a read-only lookup tool with five optional parameters and no output schema, the definition covers provenance, freshness, ordering, and result content. The remaining gap is pagination/limit behavior, minor given that the schema caps limit at 100.

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 60%, with 'company' and 'limit' undocumented in the schema. The description compensates partly by enumerating the four filter axes, making 'company' meaningful, though 'limit' is still never mentioned and no filter syntax or combination behavior is described.

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?

Names the resource and its scope precisely: 'AI/ML job postings in India from the last 7 days', plus ordering ('newest first') and payload ('direct apply links'). It does not explain how it differs from siblings like 'search' or 'browse', which is why it falls short of a 5.

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?

The filter list ('keywords, company, city or years of experience') implies when the tool is useful, but there is no explicit when-to-use or when-not-to-use statement and no reference to alternatives. Usage is inferable from the resource description 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