Skip to main content
Glama

VeritaHire live jobs

The connected person's answers to job application questions

get_my_answers
Read-only

For a connected person: their CURRENT answers to the questions employer application forms ask (contact details, work authorization, availability, pay rule, each job's dates, supervisor, may-we-contact and reason for leaving, education, references, and more), each with where it came from and how to enter it on a form. Use them word for word. Legal history, pay history, date of birth and licence numbers are never returned.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoOnly this group (default: all)
access_tokenNoNot needed when the person signed in through your Connect / sign-in button (OAuth). Otherwise the access_token from finish_connecting.

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. Added

TDQS

A3.7/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 openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: each answer carries provenance and form-entry instructions, and it explicitly states that legal history, pay history, date of birth and licence numbers are never returned.

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, followed by the content enumeration, the usage instruction, and the exclusion list. The long parenthetical enumeration is dense but each item is informative, so there is little waste.

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?

With no output schema, the description must convey the return shape, and it does: answers plus provenance plus form-entry guidance, along with explicit exclusions. Only the relationship to sibling tools is left unstated.

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?

Schema coverage is 100% and the category enum documents all sixteen groups, so the schema carries the parameter meaning. The description's enumeration loosely corresponds to those groups but does not explain the category filter or the OAuth-versus-token distinction beyond what the schema already says.

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 resource (the connected person's current answers to employer application questions) and enumerates the content groups, so an agent knows exactly what comes back. It does not explicitly distinguish itself from the nearby get_my_profile or save_answer siblings, leaving that boundary to inference.

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?

'Use them word for word' gives clear handling guidance for the returned data, and the enumeration implies the fill-out-an-application use case. However there is no explicit when-to-use versus when-not guidance and no mention of the related siblings such as get_my_profile or save_answer.

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