Skip to main content
Glama

jobs

by com.alleskralle

search_jobs

Sucht Stellenanzeigen auf alleskralle.com (DE/AT/CH) und liefert eine kompakte Liste (id, title, company, location, date). Die Bewerbungs-/Detail-URL ist NICHT in der Liste enthalten — für vollständige Details und den klickbaren Link rufe fetch_job mit der id auf. Hinweis: "remote" ist eine Volltext-Heuristik (kein strukturiertes Feld), kann also ungenau sein. Blättern nur über das zurückgegebene next_cursor möglich; die Seitenzahl ist begrenzt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSuchbegriff (Jobtitel, Tätigkeit, Skill).
cursorNonext_cursor aus einer vorherigen Antwort, um die nächste Seite zu laden.
remoteNoAuf Remote-/Homeoffice-Stellen einschränken (Heuristik).
countryNoStrikt auf ein Land einschränken: AT (Österreich), DE (Deutschland) oder CH (Schweiz). Kombinierbar mit location.
locationNoOrt, Stadt oder PLZ.

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses search scope, return format, missing detail URL, heuristic nature of 'remote', and pagination limitations. However, it does not mention authorization or rate limits.

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?

Two sentences, no fluff, front-loaded with purpose. Every sentence adds value.

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?

Given 5 parameters, no output schema, and a sibling tool, the description is thorough: it explains return fields, limitations, pagination, and relationship to fetch_job. No gaps.

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 description coverage is 100%, baseline 3. The description adds value by explaining that 'remote' is a heuristic and that cursor is for pagination. It reinforces parameter context beyond the schema.

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 clearly states the tool searches job listings on alleskralle.com (DE/AT/CH) and returns a compact list with id, title, company, location, and date. It distinguishes from the sibling tool fetch_job by noting that detail URLs are not included.

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

Usage Guidelines5/5

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

The description explains that for full details the user should call fetch_job with the id, warns that the 'remote' parameter is a heuristic, and notes that pagination is via next_cursor with limited pages. This provides explicit guidance on when and how to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All jobs toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: search_jobs retrieves a list of job listings, while fetch_job returns detailed information for a specific job by ID. There is no overlap.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: search_jobs and fetch_job, which is clear and predictable.

Tool Count3/5

With only 2 tools, the server is minimal but still covers the core search and detail retrieval workflow. However, it feels thin for a job search domain that could benefit from additional filtering or categorization tools.

Completeness4/5

The tool set provides the essential search and detail retrieval functionality. A minor gap is the lack of explicit search parameters in search_jobs (e.g., keyword, location), but the overall flow is complete for basic use.

Resources