Skip to main content
Glama

IRIS: startup intelligence

get_jobs

Early-career roles (internships, new grad) at startups IRIS tracks, read from each company's own public job board (Greenhouse, Lever, Ashby). Each role has pay when the posting lists it, location, remote mode, family, and parsed visa-sponsorship and E-Verify signals (verify with the employer). Always send the user to url, the employer's own page.

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

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNo1-50, default 20
queryNo
familyNo
remoteNo
paid_onlyNo
sponsors_visasNo
early_career_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses data provenance (parsed from Greenhouse/Lever/Ashby public boards), field coverage, and two reliability caveats (pay only present when the posting lists it; visa/E-Verify signals are parsed and should be verified). It omits pagination/rate-limit behavior and whether results are live or cached.

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?

Three tight sentences: what it returns first, then per-role attributes, then the required output behavior. No filler, and the most consequential instruction (send users to the employer's `url`) is placed last for emphasis.

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, the description takes on the job of describing the returned fields, which it does. For an 8-parameter filtered list tool, the remaining gaps are pagination/limit semantics and what `query` matches against — helpful but not essential to call it correctly.

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?

Schema description coverage is only 13% (only `limit` is documented), so the description must compensate and largely does, mapping to paid_only, city, remote, family, sponsors_visas, and early_career_only via the enumerated result attributes. The critical semantic that pay data is only present when the posting lists it warns the agent about filter behavior. `query` and result ordering remain unexplained.

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 states a specific resource and scope: early-career roles (internships, new grad) at startups IRIS tracks, sourced from companies' own public job boards. It does not explicitly contrast with a sibling, but the siblings (get_launches, get_rounds, get_market) cover clearly different resources, so misselection risk is low.

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 implied by the resource scope rather than stated: there is no 'use this when...' or exclusion of alternatives. It does provide downstream usage guidance ('Always send the user to `url`') and a caveat to verify visa signals with the employer, but nothing about when this tool is the wrong choice.

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