Skip to main content
Glama

Record whether the company got in touch

confirm_referral_contact
DestructiveIdempotent

Requires techjobs.vn sign-in. For a referral request the signed-in user sent that a referrer already referred (status referred): records whether the company got in touch with the user. Saving again updates the answer.

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": {
      "request_id": "<request_id>",
      "answer": "<answer>"
    },
    "name": "confirm_referral_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYesyes = the company contacted the user, no = it did not.
request_idYesId of one of the user's own requests, from list_referral_requests.

Output Schema

NameRequiredDescriptionDefault
actionYesThe action that was applied: resubmit or confirm_contact.
statusYesThe request's new status, when the action changed it.
request_idYes
tracker_urlYes
status_labelYes
contact_answerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses the techjobs.vn sign-in requirement and states that saving again updates the existing answer, which usefully corroborates idempotentHint=true. It does not address the destructiveHint=true flag — nothing in the description explains what could be overwritten or lost — so that annotation remains unexplained.

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?

Three short sentences, front-loaded with the auth requirement and then the state precondition, with no filler. The phrasing 'For a referral request the signed-in user sent that a referrer already referred (status referred)' is slightly convoluted but still parses correctly.

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 an output schema present, return values need not be described, and the description covers auth, the state precondition, and repeat-save behavior. The one gap is what happens when the precondition is unmet (error vs. silent no-op), which matters for a mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already carries the parameter definitions and the yes/no meaning of 'answer'. The description still adds value by constraining request_id to a user-owned request in 'referred' status, which the schema does not express.

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?

The description states a specific verb and resource — records whether the company got in touch with the user for a referral request — and scopes it to requests the signed-in user sent that are already in 'referred' status. This distinguishes it from siblings like mark_referral_request_referred or claim_referral_request without needing to open their schemas.

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?

It gives a clear precondition for use (the request must be one the user sent and already have status 'referred'), which effectively gates invocation. It does not name an alternative tool or say what to do if the request is not yet referred, so the routing guidance is implied rather than explicit.

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