Skip to main content
Glama

List jobs and models

list_jobs
Read-onlyIdempotent

Lists the jobs NL;NL Labs tests every day, what each one asks, what counts as right (the site's own words), the models and systems tested on each job and the dates covered. NL;NL Labs' own models are marked; NL;NL Desk is a system, not a model. Not open yet.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile needs no restating. The description adds genuinely useful output semantics — the per-job question, correctness criteria, models tested, and date coverage — but leaves "Not open yet" unexplained (is data gated? pending?) and says nothing about result size or ordering.

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?

It is one compact sentence enumerating the returned fields followed by two short clarifications, with the payoff information front-loaded. Despite the mangled "NL;NL" line breaks, nothing is padded or repetitive.

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?

With no output schema, the description carries the burden of describing the return shape, and it does so reasonably well by naming the fields. However, the cryptic "Not open yet" and the absence of any note on volume, pagination, or ordering leave gaps an agent must guess at for a full-catalog listing.

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, which is the baseline-4 case; there is no parameter meaning to convey. The description correctly implies a full unfiltered listing with no arguments required.

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 uses a specific verb and resource ("Lists the jobs") and enumerates what each record contains: the question asked, what counts as correct, the models/systems tested, and date coverage. It is clear what the tool returns, but it never contrasts itself with the sibling tools (get_day_results, get_model_history, get_pick), so it misses the top of the scale.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no statement of when to prefer a sibling like get_day_results, and no listed prerequisites. Only the trailing "Not open yet" acts as a caveat, and it is too ambiguous to function as real usage guidance.

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.