Skip to main content
Glama

VeritaHire live jobs

How to apply for someone honestly (the Project Dictionary Method)

get_application_method
Read-only

VeritaHire's method for helping one real person apply: choosing only strong fits, writing the resume and cover letter in the employer's words from the person's true record, filling forms from their saved answers, the steps that stay with the person (passwords, signatures, consents), and common form traps. Open to any assistant.

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

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. Changed1 schema field changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Optional"New value: +"Not needed when the person signed in through your Connect / sign-in button (OAuth). Otherwise the access_token from finish_connecting."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing what the guidance contains and the honesty constraint ('from the person's true record', steps that stay with the person), which tells an agent what to expect from the output. It stops short of describing format or length.

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 front-loaded sentence identifies the resource, followed by a compact enumeration of covered topics with no filler. The comma-spliced list is dense and slightly hard to parse, and the parenthetical title repeats content, but nothing is wasted.

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 carries the burden of saying what comes back, and it does so by listing the topics covered. For a simple read-only guidance tool with one optional parameter, that is close to sufficient; only the return format and how to use the guidance afterward are 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 single access_token parameter is fully documented in the schema, including the OAuth alternative. The description says nothing about the parameter, so it neither adds nor contradicts meaning; baseline 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 makes clear this returns VeritaHire's application method/guidance rather than performing an action, and it enumerates the content areas (choosing strong fits, resume/cover letter in the employer's words, form filling, human-only steps, form traps). This is specific enough to separate it from action siblings like save_application or get_my_answers, though it never states plainly 'returns guidance text'.

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: the phrase 'Open to any assistant' plus the framing of 'helping one real person apply' suggests when it is relevant, but there is no explicit when-to-use, no when-not, and no named alternative (e.g., get_my_profile or get_my_answers) for the adjacent needs it touches.

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