Skip to main content
Glama

Get graduate job

get_graduate_job
Read-onlyIdempotent

Read one published graduate job, permitted public address and aggregate application counts. No applicant records. Apply using the returned website URL; a filled or closed job may still have a detail page. This public endpoint returns English natural-language text, preserving sources, conditions and pagination.

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_graduate_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavior: no applicant records are exposed, closed/filled jobs still resolve, the payload is English natural-language text preserving sources, conditions and pagination, and application happens off-tool via the returned URL. That is substantive context beyond the structured fields.

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

Conciseness4/5

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

Three tight sentences with no filler, front-loaded with the operation and followed by scope exclusions and payload notes. The phrase "permitted public address and aggregate application counts" is slightly compressed and takes a re-read, but no sentence is wasted.

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 and no annotation elaboration, the description does the work of describing what comes back: address data, aggregate application counts, a website URL, English text, plus source/condition/pagination preservation. For a one-parameter read, the only real gap is the absence of any hint about how to obtain a valid id.

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 0% for the single required `id` parameter, so the description must carry the load. It implies the parameter selects one job ("one published graduate job") but never states that `id` is a job identifier, its expected form, or how an agent obtains it. The regex/length constraints live only in the schema, unmentioned 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 opens with a specific verb+resource: "Read one published graduate job," and scopes it to the public detail record rather than a listing. It also carves out what is excluded ("No applicant records"), which sharpens the boundary with application-related siblings. It stops short of naming search_graduate_jobs as the alternative, so sibling differentiation is implied by "one" rather than stated.

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?

Usage guidance is present but indirect: "Apply using the returned website URL" tells the agent what to do after retrieval, and "a filled or closed job may still have a detail page" warns that a non-open status is not a reason to skip this call. There is no explicit statement of when to use this versus search_graduate_jobs, and no prerequisite (e.g., where the id comes from).

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