Skip to main content
Glama

Hire the AI crew

hire_crew

Put an AI crew member (name, voice, role) on every free phone line so the crew can dial. Run after a number is bought.

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": "hire_crew"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation. The description usefully adds that the operation applies to *every* free phone line rather than one line, which is real scope information the annotations don't carry. However, it says nothing about cost/credit consumption (notable given sibling tools buy_credits and credits_status), idempotency, or what happens to lines already occupied by a crew member.

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, front-loaded with the action and its effect, followed by the prerequisite. Very little waste; only the '(name, voice, role)' parenthetical is questionable overhead given there are no matching parameters.

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 zero-parameter tool with no output schema, the definition covers what it does and when to run it. It leaves out operationally relevant facts: whether hiring consumes credits, whether it is idempotent, and what the caller can expect on failure or partial success across multiple lines.

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?

The tool takes zero parameters, which normally sets a baseline of 4. But the parenthetical '(name, voice, role)' implies configurable inputs that do not exist in the empty schema, creating ambiguity about how a crew member's identity is specified. That ambiguity pulls the score down from the baseline.

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?

The description gives a concrete verb and resource: 'Put an AI crew member ... on every free phone line'. It also states the effect's purpose ('so the crew can dial'), which distinguishes it from setup tools like buy_number. It doesn't name a sibling explicitly, so it falls short of a 5.

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?

'Run after a number is bought' gives a clear ordering prerequisite that maps to buy_number. There is no guidance on when NOT to run it, or what happens if the crew is already hired, so it stops short of explicit when/when-not/alternatives.

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.