Skip to main content
Glama
mod-us

Modus MCP Server

Official
by mod-us

modus_get_open_positions

Retrieve open job requisitions and hiring forecast by quarter, including status, department, and planned start dates for headcount planning.

Instructions

Get open job requisitions and hiring forecast by quarter. Returns open positions with status, department, and planned start dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by requisition status. Default: OPEN
departmentNoFilter by department name

Implementation Reference

  • Tool definition and input schema for modus_get_open_positions, registered in the TOOLS array with name, description, and inputSchema (status enum, department filter).
    {
      name: "modus_get_open_positions",
      description:
        "Get open job requisitions and hiring forecast by quarter. Returns open positions with status, department, and planned start dates.",
      inputSchema: {
        type: "object",
        properties: {
          status: {
            type: "string",
            enum: ["OPEN", "DRAFT", "CLOSED", "ALL"],
            description: "Filter by requisition status. Default: OPEN",
          },
          department: {
            type: "string",
            description: "Filter by department name",
          },
        },
      },
    },
  • Handler implementation for modus_get_open_positions in the CallToolRequestSchema switch statement. Fetches from /api/open-headcount, filters by status and department, builds summary stats, and returns formatted response.
    case "modus_get_open_positions": {
      const { status, department } = args || {};
    
      // Fetch all open positions
      response = await modusApi.get(`/api/open-headcount`);
    
      // Extract jobs array from response data
      const data = response.data || {};
      let positions = data.jobs || [];
    
      if (status && status !== "ALL") {
        positions = positions.filter(pos => pos.atsStatus === status);
      }
      if (department) {
        positions = positions.filter(pos =>
          pos.department?.name?.toLowerCase().includes(department.toLowerCase())
        );
      }
    
      // Add summary (using the stats from the API response)
      const summary = {
        total: positions.length,
        hired: data.hired || 0,
        open: data.open || 0,
        notOpen: data.notOpen || 0,
        offerPending: data.offerPending || 0,
        readyToRecruit: data.readyToRecruit || 0,
        byStatus: {},
        byDepartment: {},
        byQuarter: {},
      };
    
      positions.forEach((pos) => {
        if (pos.atsStatus) {
          summary.byStatus[pos.atsStatus] = (summary.byStatus[pos.atsStatus] || 0) + 1;
        }
        if (pos.department?.name) {
          summary.byDepartment[pos.department.name] = (summary.byDepartment[pos.department.name] || 0) + 1;
        }
        if (pos.hiringQuarter?.name) {
          summary.byQuarter[pos.hiringQuarter.name] = (summary.byQuarter[pos.hiringQuarter.name] || 0) + 1;
        }
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              {
                summary,
                openPositions: positions,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • ListToolsRequestSchema handler that exposes the TOOLS array (including modus_get_open_positions) to clients via the MCP protocol.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: TOOLS,
      };
    });
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It does not disclose whether the operation is read-only, requires authentication, or has any side effects. Only minimal return fields are mentioned, leaving behavioral traits unclear.

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?

The description is two sentences, front-loads the verb 'Get', and contains no superfluous information. Every word contributes to clarity.

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 and no annotations, the description is moderately complete. It lists return fields but omits details on the forecasting portion and pagination or limits. For a simple tool with optional parameters, it is adequate but not comprehensive.

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%, with both parameters described clearly in the schema. The description adds the 'by quarter' context but does not enhance parameter understanding beyond what the schema provides. Baseline 3 is appropriate.

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?

The description clearly states the tool retrieves open job requisitions and a hiring forecast by quarter, specifying the resource and adding value beyond the name. It distinguishes from sibling tools like modus_get_current_headcount by focusing on open positions and forecasting.

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 description implies usage for quarterly hiring data but provides no explicit guidance on when to use this tool versus alternatives like modus_get_hiring_timeline or modus_get_team_performance. No exclusionary context is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mod-us/modus-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server