Skip to main content
Glama

Superintelligence.jobs

Search open roles

search_jobs
Read-onlyIdempotent

Search open frontier-AI roles. Filters combine (AND). Returns compact records; use get_job for full detail.

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

Input Schema

NameRequiredDescriptionDefault
modeNoRemote, Hybrid or On-site
levelNoe.g. Senior, Staff, Entry
limitNoResults per page (default 25)
queryNoKeyword across title, summary, category, skills
offsetNoPagination offset
companyNoOrganization name or id, e.g. "Anthropic"
countryNoCountry name, e.g. "United States"
categoryNoe.g. Engineering, Research, Policy
remoteOnlyNoRemote roles only

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior — filters AND together rather than OR, and results are compact rather than full records — but says nothing about pagination caps, sorting, or empty-result behavior.

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 short sentences, front-loaded with purpose, then the filter semantics, then the routing escape hatch. Nothing is wasted and nothing important is buried.

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?

With no output schema, the description does the minimum needed by signaling that returns are compact records and that get_job exists for full detail. It could go further by naming which fields survive in the compact form, but the essential call-shape information is present.

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%, so all nine parameters are self-documenting with examples and bounds. The description adds no parameter-level meaning beyond the AND-combination note, so the baseline 3 applies.

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?

The description gives a specific verb and resource ("Search open frontier-AI roles") plus a scope qualifier that narrows the corpus, so the agent knows exactly what it queries. It also names the sibling get_job as the detail path, though it doesn't distinguish itself from the other siblings (market_stats, list_orgs, diff_since).

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?

"use get_job for full detail" names an alternative and the condition that selects it, and "Filters combine (AND)" tells the agent it can stack filters. There is no when-not guidance (e.g. no guidance on when market_stats or list_orgs is the better entry point), so it falls short of a full 5.

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