Skip to main content
Glama

Job Alerts: internships and new-grad roles

List tracks

list_tracks
Read-onlyIdempotent

The job tracks the track filter takes (swe, data-ai, quant, ...), with open early-career role counts across every country.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful scope detail — counts are limited to open early-career roles and aggregated across every country — but says nothing about result ordering, whether counts are live, or what the response entries look like.

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?

It is a single sentence with no padding, but it is not front-loaded with a clear verb and the awkward construction 'The job tracks the track filter takes' costs the reader a re-read. A leading clause like 'List job tracks...' would have made it much clearer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only tool with no output schema, the description should define the shape of the return value. It identifies the two payload elements (track identifiers and per-country open early-career counts) but leaves response structure and aggregation semantics unstated.

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

Parameters4/5

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

The tool takes zero parameters and the input schema is an empty object, so there is no parameter semantics to clarify. The description needs only to describe the returned data, which it does at a high level.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that the tool returns job tracks together with open early-career role counts by country, but it never states a verb and the phrasing 'The job tracks the track filter takes' is syntactically tangled, forcing the agent to reconstruct the purpose. It gives the resource implicitly (track values) but offers no differentiation from siblings such as list_companies or search_roles.

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: by saying these are the tracks 'the track filter takes', it hints the results can be used as filter values elsewhere, but it never names the consuming tool or states when to call this versus search_roles or list_groups. There are no explicit when-not conditions.

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.