Skip to main content
Glama

Job Alerts: internships and new-grad roles

List companies

list_companies
Read-onlyIdempotent

Companies with open early-career roles, most roles first, with their groups and ATS. open_roles counts every country. Pass a name to the company filter of search_roles exactly as returned here.

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

Input Schema

NameRequiredDescriptionDefault
groupNoOnly companies in any of these groups; an array or a comma-separated string.
limitNoDefault 100.
queryNoPart of the company name or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful behavioral context: ordering by role count, inclusion of groups and ATS, and the caveat that open_roles counts every country. It says nothing about pagination or total counts beyond the schema's limit default, so a 3 is appropriate.

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?

Two tightly packed sentences with no filler; the resource and ordering are front-loaded before the chaining instruction. Every clause carries information an agent needs.

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 read-only three-parameter list tool with no output schema, the description covers what is returned (companies plus groups and ATS), how results are ordered, and a subtle counting caveat. Only pagination behavior and the meaning of the group filter relative to list_groups are left implicit, which is minor.

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 100%, so all three parameters (group, limit, query) are already documented in the schema, which sets the baseline at 3. The description adds only the instruction about passing an exact name into search_roles, not clarifying syntax or format beyond what the schema provides.

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

Purpose5/5

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

Names a specific resource (companies with open early-career roles), the ordering ("most roles first"), and the payload contents (their groups and ATS). This clearly distinguishes it from search_roles and list_groups, so an agent can differentiate it without inspecting schemas.

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

Usage Guidelines4/5

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

Gives concrete downstream guidance: pass a returned name into the company filter of search_roles exactly as returned, which implies this is the discovery step feeding search_roles. It does not state explicit when-not-to-use conditions or contrast with list_groups, so it falls short of full alternative 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.