Skip to main content
Glama

AceRound AI Interview Copilot

submit_job_apply_sms_code

Give the SMS code the user received to the apply AI, the same as typing it into the code box at the top of the app's main window: if the AI is still waiting, the code goes straight to that wait and the turn continues; if the wait has ended, it is sent to that conversation as a message. taskId can be omitted when only one application is waiting; pass it when several are (see get_job_apply_client_status). Says so if nothing is waiting for a code. Replies with the employer / role it went to. Requires the AceRound Auto Apply desktop app on the user’s computer to be signed in and open (running in the background after closing the window also works); if the app is offline or outdated, the tool says so. (Requires the user's sign-in with scope job_applications:write.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "submit_job_apply_sms_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe SMS code
taskIdNoConversation id (taskId), from get_job_apply_client_status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare it is not read-only, not destructive, and closed-world; the description adds substantial context beyond that: the code is routed either into an active wait or as a conversation message, the tool reports the employer/role it went to, and it requires the desktop app to be signed in and open. The auth scope (job_applications:write) and offline/outdated-app behavior are also disclosed. Minor gap: no mention of rate limits or what happens if the code is wrong/expired.

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?

Front-loaded with the core action and the routing behavior, then prerequisites and auth. It is a dense single paragraph with some parenthetical asides, but nearly every clause carries operational information; slight tightening would help readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description states what is returned (the employer/role the code went to) and covers prerequisites, auth scope, and error signaling. For a two-parameter mutation tool, an agent has everything needed 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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains the conditional necessity of taskId and its provenance, and clarifies that 'code' is the SMS code the user received. That goes beyond the schema's terse field descriptions.

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?

States a specific verb and resource ('Give the SMS code ... to the apply AI') and anchors it to a concrete UI equivalent (typing into the code box). It is clearly distinguishable from siblings like get_job_apply_client_status, which it names as the source of taskId.

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

Usage Guidelines5/5

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

Explicitly says when taskId can be omitted (only one application waiting) versus when to pass it (several waiting), and points to get_job_apply_client_status for obtaining it. It also states the failure case ('Says so if nothing is waiting for a code'), leaving little to inference.

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