Skip to main content
Glama

Inserat abrufen

get_job
Read-onlyIdempotent

Ruft ein einzelnes Stelleninserat von funkyjobs.ch ab: Titel, Arbeitgeber, Ort, Pensum, Lohn falls angegeben, und einen Auszug der Beschreibung. Das vollständige Inserat und der Weg zur Bewerbung stehen unter dem mitgelieferten Link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDie id eines Treffers aus search_jobs.

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 and openWorldHint, so safety and idempotency are covered. The description adds genuinely useful behavioral context by disclosing that the description text is only an excerpt and the full listing plus application path are behind the returned link, but it says nothing about error behavior for an invalid id or any 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, both front-loaded and waste-free: the first states the retrieval plus returned fields, the second adds the only extra fact the agent needs (excerpt vs. full listing via link). Nothing is redundant.

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?

There is no output schema, so the description must describe the return shape, and it does so well by listing title, employer, location, Pensum, optional salary, an excerpt and a link. It is nearly complete; only failure/empty-result behavior is unaddressed.

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 single id parameter is fully documented as 'Die id eines Treffers aus search_jobs'. The description adds no additional meaning about the parameter, so the schema carries the full burden and the baseline of 3 applies.

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 opens with a specific verb and resource ('Ruft ein einzelnes Stelleninserat von funkyjobs.ch ab') and enumerates the returned fields, which clearly distinguishes it from the plural-listing sibling search_jobs. An agent knows exactly what it fetches without opening the schema.

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 word 'einzelnes' (single) implies this is for retrieving one specific listing rather than searching, but the description never explicitly says when to use it versus search_jobs or that the id must come from a prior search. That routing information lives only in the schema, so usage is implied 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