Skip to main content
Glama

VeritaHire live jobs

Questions the connected person has not answered yet

get_my_gaps
Read-only

For a connected person: the common application questions they have not answered yet, and the facts missing for each job in their work history. Ask them all in one message BEFORE opening an employer's form, so the form never stops half-way. Leave include_role_specific off when asking the person what to fill in. Set it only while filling one employer's form: it returns, in a separate list, questions only some jobs ask (polygraph, CDL, security clearance, sales numbers) - ask the person only the ones that form actually asks.

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_my_gaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
access_tokenNoNot needed when the person signed in through your Connect / sign-in button (OAuth). Otherwise the access_token from finish_connecting.
include_role_specificNoOnly while filling a specific form; default off

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / access_token / description
      Previous value: -"From finish_connecting"New value: +"Not needed when the person signed in through your Connect / sign-in button (OAuth). Otherwise the access_token from finish_connecting."
    • removedInput schema / required
      Removed value: -[
      -  "access_token"
      -]
  2. Changed1 schema field changed
    • addedInput schema / properties / include_role_specific / description
      Added value: +"Only while filling a specific form; default off"
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so the description does not need to argue safety. It still adds real behavioral context beyond them: results come back as lists, and role-specific items arrive in a separate list that must be filtered against what a given form actually asks. It does not say what happens when nothing is missing or how the two lists are shaped, which keeps it short of a 5.

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?

Purpose is front-loaded in the first clause and every sentence carries an instruction an agent needs before calling the tool. The third sentence is dense with parenthetical examples and a conditional, which costs some readability, but nothing is filler.

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?

With no output schema and only two optional parameters, the description carries the return-shape burden and does so: it distinguishes the main list from the separate role-specific list and explains what each contains. Combined with the safety annotations and the pre-form workflow instruction, an agent has what it needs to call this 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 genuinely extends include_role_specific: it explains the consequence of enabling it (a separate list of questions only some jobs ask, with concrete examples like polygraph, CDL, security clearance) and the operational rule for toggling it. That is meaning the schema's one-line property description does not carry.

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 names the exact resource returned: the connected person's unanswered common application questions plus the facts missing for each job in their work history. That is specific enough to separate it from get_my_answers (answers already on file) without opening either schema.

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?

It states both the timing and the reason to use it ('Ask them all in one message BEFORE opening an employer's form, so the form never stops half-way') and gives an explicit include/exclude rule for the role-specific mode: leave it off when interviewing the person, set it only while filling one employer's form.

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