Skip to main content
Glama

Job Alerts: internships and new-grad roles

List company groups

list_groups
Read-onlyIdempotent

Company groups the group filter takes: curated lists (faang, ai-companies, quant-hft, ...) and sectors, with member counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds one piece of return context, member counts being included, but says nothing about ordering, pagination, or whether the group set is fixed.

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?

A single sentence with no wasted wording and the key content (examples, member counts) front-loaded. The phrasing is a slightly awkward fragment ("Company groups the group filter takes:") but remains parseable.

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 trivial zero-param enumerator this is close, but with no output schema the description is the only source of return-shape information and it gives only partial coverage (examples and member counts). It also leaves "the group filter" unnamed, so an agent must guess which sibling consumes these values.

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, so there is no parameter meaning to convey; the baseline applies. The description correctly implies no input is required to enumerate the groups.

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?

States a specific resource (company groups) plus concrete contents: curated lists such as faang, ai-companies, quant-hft, and sectors. That is enough to differentiate it from list_companies or list_tracks, though it never explicitly contrasts with those siblings.

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?

The phrase "the group filter takes" implies the tool exists to discover valid filter values, but it never states when to call it versus alternatives, nor whether results are stable or exhaustive. Usage is inferable rather than stated.

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.