Skip to main content
Glama

VeritaHire live jobs

Connect the job seeker's VeritaHire account

connect_my_account

Only for assistants that cannot sign in with OAuth (ChatGPT and Claude use their own Connect / sign-in button instead). For a person with a VeritaHire account who wants your help applying for jobs. Returns a link and a short code. The person opens the link on veritahire.com, signs in themselves and clicks Allow; then call finish_connecting with pair_secret. Takes no personal data. Never ask the person for their VeritaHire password or sign-in code.

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

Input Schema

NameRequiredDescriptionDefault
ai_nameNoYour name as the person will see it on the Allow page, e.g. "Claude" or "ChatGPT"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations are sparse (readOnlyHint=false, destructiveHint=false), so the description carries the load and does: it discloses the return shape (link + short code), the human-in-the-loop step on veritahire.com, that no personal data is taken, and a security constraint against requesting passwords. Nothing here contradicts the annotations.

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?

The eligibility restriction is front-loaded where it matters most, and the flow is laid out in order. A few sentences ("Takes no personal data", the password warning) are security-relevant rather than waste, though the phrasing is slightly clipped in places.

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 explains what is returned, who does what on the Allow page, how the flow completes, and the privacy boundary. For a one-parameter linking tool this is sufficient to call it correctly.

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?

There is a single parameter (ai_name) with full schema description coverage including an example, so the schema already does the work. The description adds no further meaning about how ai_name is displayed or whether it is optional, leaving it at the baseline.

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?

The description states a specific outcome: it initiates account linking for a VeritaHire account holder and "Returns a link and a short code." It also distinguishes itself from both the OAuth sign-in path and the follow-up sibling, naming finish_connecting as the next step.

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?

Explicit when-to-use and when-not-to-use: "Only for assistants that cannot sign in with OAuth (ChatGPT and Claude use their own Connect / sign-in button instead)." It also names the exact follow-up call (finish_connecting with pair_secret), so the agent knows the full flow.

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