Skip to main content
Glama

VeritaHire live jobs

Finish connecting after the person clicked Allow

finish_connecting

Exchanges pair_secret (from connect_my_account) for an access_token once the person has clicked Allow on veritahire.com. Returns status waiting_for_person until then. The token reads only what the person allowed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pair_secret": "<pair_secret>"
    },
    "name": "finish_connecting"
  }
}

Input Schema

NameRequiredDescriptionDefault
pair_secretYesFrom connect_my_account

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world call. The description adds genuinely useful behavior beyond that: the waiting_for_person interim status and the fact that the resulting token is scoped to what the person allowed. It stops short of describing token lifetime, error cases, or what happens on repeated calls despite idempotentHint=false.

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?

Three short sentences, front-loaded with the action, then the precondition, then the interim return state. No filler.

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 one-parameter tool with no output schema, the description covers the action, precondition, interim return value, and token scope. Only edge cases (expired secret, repeated invocation) are unaddressed, which is a minor gap.

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 parameter already carries the description 'From connect_my_account', so the description's mention of pair_secret's origin largely restates the schema. Baseline 3 applies since the schema does the work.

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?

States a specific verb and resource ('Exchanges pair_secret ... for an access_token') and ties it to the sibling connect_my_account as the source of the secret, so an agent can distinguish the two steps of the flow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Makes the precondition explicit ('once the person has clicked Allow on veritahire.com') and tells the agent what to expect before that point ('Returns status waiting_for_person until then'). It does not spell out a polling cadence or an explicit 'do not call before connect_my_account' exclusion, but the sequencing is clear.

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