Skip to main content
Glama
Sign In

Applystead

by com.applystead
OverviewDiscussionsAdmin

Call from the recruiter line

call_line
Destructive

Calls a US or Canadian number the member names from their own recruiter line (needs an Applystead membership): the member's phone rings first, then the number is dialed. The member confirms; nothing is dialed otherwise. Actions: dial. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "call_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Adds concrete behavior beyond the annotations: the member's phone rings first, the target number is dialed second, an Applystead membership is required, and no dial occurs without confirmation. This meaningfully supplements the destructive/open-world hints with authentication and sequencing detail.

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?

Four short sentences, front-loaded with purpose and call flow, with no filler. The action/help line is compact and operational.

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 destructive, open-world calling tool, the description covers the membership prerequisite, confirmation requirement, and call sequence. It leaves the dial payload to the help action, which is a reasonable but not fully self-contained design, and no output schema requires return-value explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description merely repeats the schema's action/help mechanism instead of explaining what fields the 'dial' action requires. An agent must call the help action to learn the payload, so the description adds little parameter meaning beyond the schema.

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 ('Calls') and resource ('a US or Canadian number... from their own recruiter line') and clearly describes an outbound call flow rather than line retrieval, making it distinct from the get_line sibling.

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?

Specifies the membership prerequisite and the confirmation gate ('member confirms; nothing is dialed otherwise'), giving clear usage context. It does not explicitly name an alternative tool or state when not to use it, so it falls short of full routing guidance.

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

All Applystead toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources