Skip to main content
Glama

Kariaa Agents

Open a job

get_job
Read-only

Use when the person wants the details of one result from search_jobs: description, requirements, pay when stated, posted date and how to apply. Use it before applying, or to tailor a resume or cover letter to the posting.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesA job_id from search_jobs

Output Schema

NameRequiredDescriptionDefault
payNoPay when stated
urlNoWhere to apply
titleNoTitle
job_idNoJob id
companyNoEmployer
descriptionNoThe posting
how_to_applyNoHow to apply
requirementsNoRequirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered; the description adds that the record is a specific job posting with the enumerated content an agent can expect. It says nothing about behavior for stale or removed job_ids, and no auth or rate-limit context, but for a read-only lookup the disclosure is solid.

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 tight sentences: the first front-loads the trigger and the payload, the second supplies the decision context. No redundant restatement of the name or title and no filler.

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?

An output schema exists, so return values need not be explained, and the description still sketches the payload usefully. For a one-parameter read tool this is close to complete; only edge-case behavior (expired or invalid job_id) 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?

The single job_id parameter has 100% schema description coverage, and the schema already states it is 'A job_id from search_jobs'. The description restates that provenance but adds no format, length, or validation guidance beyond the schema, so the baseline of 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?

States a specific verb and resource: fetch the details of a single job result from search_jobs, and enumerates the fields it returns (description, requirements, pay when stated, posted date, how to apply). It clearly separates itself from the list-oriented search_jobs as the single-record expansion, but never distinguishes itself from other detail-ish siblings such as check_job_post.

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?

Gives explicit trigger conditions — 'Use when the person wants the details of one result from search_jobs' — and concrete follow-on contexts: before applying, or to tailor a resume or cover letter. No when-not guidance or prerequisites (e.g., that the job must still be listed) are 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.