Skip to main content
Glama

Virtual Assistant Capital

Get hiring process and terms

get_hiring_process
Read-onlyIdempotent

Returns how hiring through Virtual Assistant Capital works: the steps, timelines, standard terms, service limits and where to send a request.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the actual substance of the response (steps, timelines, terms, limits, submission channel), which matters because there is no output schema. It stops short of saying whether the content is static or account-specific.

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?

A single sentence, front-loaded with the verb and subject, followed by a compact enumeration of what the caller will receive. Every clause carries information and nothing is repeated from the title or annotations.

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 no-argument, read-only informational tool with no output schema, the description adequately sets expectations about the returned content. The only real gap is that 'where to send a request' is left abstract — the agent cannot tell whether it means a URL, email, or a follow-up tool call.

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?

The tool takes zero parameters and additionalProperties is false, so there is nothing for the description to disambiguate. The baseline applies; no parameter-level guidance is needed or missing.

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 names a specific verb ('Returns') and a specific resource ('how hiring through Virtual Assistant Capital works'), then enumerates the contents: steps, timelines, standard terms, service limits, and request routing. It is clearly an informational lookup rather than a pricing or service-catalog tool, though it never explicitly contrasts itself with siblings like get_plans_and_pricing or get_service_details.

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?

Usage is only implied by the content listed — an agent can infer this is the tool for 'how does hiring work / what are the terms' questions. There is no explicit when-to-use statement, no when-not-to-use, and no pointer to an alternative for pricing or per-service detail, which the sibling names suggest exist.

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