Skip to main content
Glama
mod-us

Modus MCP Server

Official
by mod-us

modus_get_ramp_profiles

Retrieve ramp time profiles showing how quickly new hires achieve full productivity, with monthly percentages per role.

Instructions

Get ramp time profiles showing how long new hires take to reach full productivity. Returns month-by-month productivity percentages by role.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoJob role to get ramp data for (e.g., 'Account Executive')

Implementation Reference

  • Schema definition for modus_get_ramp_profiles tool - defines the tool name, description, and input schema (optional 'role' parameter)
    {
      name: "modus_get_ramp_profiles",
      description:
        "Get ramp time profiles showing how long new hires take to reach full productivity. Returns month-by-month productivity percentages by role.",
      inputSchema: {
        type: "object",
        properties: {
          role: {
            type: "string",
            description: "Job role to get ramp data for (e.g., 'Account Executive')",
          },
        },
      },
    },
  • Handler implementation for modus_get_ramp_profiles - extracts the 'role' argument, builds query params, calls the /api/sales/ramp-profiles API endpoint, and returns the response data
    case "modus_get_ramp_profiles": {
      const { role } = args || {};
      const params = new URLSearchParams();
    
      if (role) params.append("role", role);
    
      response = await modusApi.get(`/api/sales/ramp-profiles?${params.toString()}`);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
Behavior3/5

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

No annotations provided; description indicates it is a read-only data retrieval (returns percentages). Does not disclose behavior for invalid roles or data sources, but basic behavioral transparency is present.

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?

Two sentences: first states purpose, second details output. Front-loaded and efficient, though 'time profiles' is slightly redundant with the explanation that follows.

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?

Despite no output schema, the description clearly explains the return format ('month-by-month productivity percentages by role'). Single optional parameter is well-defined. Adequately complete for a simple data retrieval tool.

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 the 'role' parameter already described. The description adds no additional meaning beyond what the schema provides, so baseline score of 3 applies.

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?

Clearly states the verb 'Get' and the resource 'ramp time profiles' with specific output: 'month-by-month productivity percentages by role'. Distinct from sibling tools which focus on attrition, benchmarks, headcount, etc.

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?

Implies usage when ramp data is needed, but provides no explicit when-to-use or when-not-to-use guidance. No mention of alternatives among 13 sibling tools.

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