Skip to main content
Glama

VeritaHire live jobs

The connected person's applications

get_my_applications
Read-only

For a connected person: the applications VeritaHire holds for them (employer, title, status, date, link), so nothing is applied to twice.

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

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.

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, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that: it scopes the result to the authenticated 'connected person' (an implicit prerequisite of having connected an account) and lists the returned fields, which matters because no output schema exists.

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?

One compact sentence with the scope stated first and the field list in a parenthetical, so nothing is buried. The closing rationale phrase is slightly informal but earns its place as a usage cue.

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 single-parameter read tool with no output schema, the description covers the scope, the prerequisite (being connected), and the shape of the result. It omits edge cases such as an empty result set or ordering, but nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100% and the single access_token parameter is fully documented in the schema, including the OAuth exception. The description adds nothing about the parameter, so the baseline of 3 applies.

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 applications VeritaHire holds for the connected person — and enumerates the fields returned (employer, title, status, date, link). An agent knows exactly what it retrieves, though it never distinguishes itself from siblings like save_application or get_application_method.

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?

The trailing clause 'so nothing is applied to twice' implies the intended use — checking existing applications before applying — but the guidance is indirect and no alternative tool or exclusion condition is named. Usage is inferable rather than stated.

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