Skip to main content
Glama

Job Alerts: internships and new-grad roles

Get role

get_role
Read-onlyIdempotent

One role by its numeric id, including closed roles (status "closed", apply_url null). apply_url is the link to send a person to. With a Realtime key, employer_url is the employer posting (fetch it for the description) and ats_job_id the ATS id; both are null otherwise. include_evidence is Realtime.

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

Input Schema

NameRequiredDescriptionDefault
idYesRole id from search_roles or a /roles/<id> link.
include_evidenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover the readOnly/idempotent/non-destructive safety profile, and the description adds genuinely new behavior: closed roles are still returned (status "closed", apply_url null), and employer_url and ats_job_id are only populated under a Realtime key and null otherwise. That auth-tier-conditional field population is exactly the kind of context structured fields do not carry.

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?

Front-loaded with the primary purpose, then conditional field semantics, with no filler sentences. Some clauses are telegraphic to the point of ambiguity ("include_evidence is Realtime."), which costs a point on clarity.

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?

For a two-parameter read with no output schema, the description usefully names the key return fields (status, apply_url, employer_url, ats_job_id) and when they are null. What remains thin is the include_evidence parameter, whose effect on the response is never spelled out.

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 coverage is 50%: the id parameter is already documented in the schema, so the description only reinforces that ids are numeric. For the undocumented include_evidence it offers a single terse clause ("include_evidence is Realtime"), which hints that it only matters for Realtime keys but does not explain what evidence is included or the default. Partial compensation for the coverage gap, not full.

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 first clause states a specific verb+resource and scope: fetch a single role by numeric id, explicitly including closed roles. That singular-by-id framing distinguishes it from search_roles without needing to name it. It stops short of a 5 because it never explicitly contrasts itself with the sibling finder tools.

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 is only implied: you call it when you already have a role id (the schema points to search_roles or a /roles/<id> link as the id source). There is no explicit when-to-use/when-not or statement of the alternative path for discovery, so an agent must infer the routing.

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.