Skip to main content
Glama

Jobs Brief: hand-picked cloud, DevOps & AI infrastructure jobs, EU remote + Poland

Hand-picked cloud and DevOps roles from a past Jobs Brief edition

sample_edition
Read-onlyIdempotent

A hand-picked selection, a few dozen roles, not an exhaustive job search: senior cloud, platform, DevOps, SRE and AI-infrastructure roles from a past Jobs Brief edition, each read by an editor and kept only if it can be taken remotely from anywhere in the EU ('remote-eu') or from Poland ('poland'), at mid, senior or manager level. Each role has its location, contract form where stated, core stack, a one-line summary of the work, the published salary when there is one, and a link to the company's own posting. All filters are optional and combine.

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

Input Schema

NameRequiredDescriptionDefault
levelNomid: evidenced mid-level IC roles. senior: senior, staff and principal IC roles. manager: engineering managers and heads of engineering.
queryNoFree text matched against title, company and summary, e.g. 'observability' or 'GPU'.
stackNoA technology to match in the role's stack, e.g. kubernetes, terraform, aws, gcp.
sectionNoremote-eu: remote roles open across the EU. poland: roles based in Poland.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / level / description
      Added value: +"mid: evidenced mid-level IC roles. senior: senior, staff and principal IC roles. manager: engineering managers and heads of engineering."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the data is a frozen past edition, capped at a few dozen entries (implying no pagination concerns), editor-curated with explicit inclusion criteria, and it enumerates the returned fields. That is real context beyond the annotations.

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

Conciseness3/5

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

The opening clause is well front-loaded ('A hand-picked selection, a few dozen roles, not an exhaustive job search'), but the rest is a single long run-on sentence packing curation rules and the return-field list together. Every fact earns its place, yet the packaging makes the return fields easy to miss.

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 correctly compensates by enumerating returned fields (location, contract form, stack, one-line summary, salary, link). Curation rules and the non-exhaustive size limit are also given. The only gap is that the relationship to the sibling tool is left unstated.

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 an extra point by stating that all filters are optional and combine — conjunction semantics the schema itself does not express — and by tying the level and section values to the curation criteria described in prose.

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 states a specific resource and scope: senior cloud, platform, DevOps, SRE and AI-infrastructure roles drawn from a past Jobs Brief edition, filtered to remote-EU or Poland and to mid/senior/manager level. An agent knows exactly what this returns. It does not contrast itself with the sibling 'signals' tool, so it stops 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?

'not an exhaustive job search' and 'a few dozen roles' signal the boundary — this is a curated snapshot, not a comprehensive listing — which is useful negative guidance. However, no alternative tool is named for a full search, and there is no explicit statement of when to prefer this over 'signals'; the routing must be inferred.

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