Skip to main content
Glama

VeritaHire live jobs

The connected person's job settings

get_my_profile
Read-only

For a connected person: their name, search area, job types, keywords, and how many applications and saved answers VeritaHire holds for them.

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

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.6/5.0
Behavior3/5

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

The annotations already declare this as a safe read-only, closed-world operation with no destructive behavior. The description adds useful content detail by saying it returns profile fields and counts rather than full application or answer records, but it does not elaborate on authentication behavior, response structure, or any rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single efficient sentence that front-loads the audience context and then lists the returned profile contents. Every phrase carries information, and there is no redundant or filler wording.

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 low-complexity read tool with one optional auth parameter and no output schema, the description is mostly complete because it enumerates the profile fields and counts returned. It would be stronger if it explicitly stated that it returns a summary rather than full application/answer records, but the core contents are covered.

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 one optional access_token parameter with full schema description coverage. The description does not mention the parameter at all, so it adds no meaning beyond the schema; a baseline of 3 is appropriate when the schema already documents the only parameter.

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 identifies the resource clearly by listing the connected person's profile fields: name, search area, job types, keywords, and counts. It implies a retrieval operation through the tool name but does not use an explicit verb like 'get' or 'returns,' and it does not explicitly name sibling tools such as get_my_applications or get_my_answers.

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 phrase 'For a connected person' establishes a prerequisite context, implying the tool is for a signed-in/OAuth-connected user. However, it gives no explicit when-to-use guidance versus get_my_applications or get_my_answers, nor does it state when not to use this profile summary.

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