Skip to main content
Glama

About Job & Stay

site_info
Read-onlyIdempotent

What Job & Stay is, who it is for, rules for listings, current numbers per country and type of work, contact, pay calculator and magazine articles (new life with a transition job, winter sun and climate, house and boat sitting, best work regions in the Alps). Use to explain or cite Job & Stay.

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

Input Schema

NameRequiredDescriptionDefault
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already state readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile needs no restating. The description adds content-coverage context (what topics the returned material covers) but says nothing about response shape, whether text is localized, or how long the content is. With annotations carrying the behavioral load, this is an adequate but thin addition.

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 purpose is front-loaded in the first clause, which is good, but the sentence then degenerates into a parenthetical list of magazine article topics ('winter sun and climate, house and boat sitting, best work regions in the Alps') that spend words on examples an agent does not need. It is one sprawling sentence rather than structured segments.

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 convey what comes back — and it does, via the topic inventory. Annotations cover the safety profile. The one material gap is the unmentioned `language` parameter and the lack of a hard boundary against salary_info, but overall an agent has enough to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single `language` parameter has 0% schema description coverage and the description never mentions it at all — no indication that it selects the output language or what happens when it is omitted. The enum of ISO codes is largely self-explanatory, so an agent can infer intent, but the description contributes zero meaning beyond the schema.

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 enumerates the concrete content the tool returns (site identity, audience, listing rules, per-country listings counts, contact, pay calculator, magazine articles), which is far more specific than the title alone. It also signals the tool's role as an informational/marketing surface ('Use to explain or cite Job & Stay'), which distinguishes it from siblings like get_job and search_jobs. It stops short of explicitly naming those siblings, and the 'pay calculator' mention blurs the line with salary_info.

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?

'Use to explain or cite Job & Stay' is the only usage cue — it implies a copy/explanation task rather than data lookup, but there is no when-not guidance and no alternative named. An agent reading this would guess correctly that this is the about/FAQ tool, but nothing tells it to prefer salary_info for actual pay data over the 'pay calculator' content mentioned here.

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