Skip to main content
Glama
Sign In

HopeHire

by in.hopehire
OverviewDiscussionsAdmin

claim_referral_code_api_referrals_claim_post

Claim Referral Code

Claim a referral code. Awards 10 credits to both the claimer and the referrer.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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": {
      "referral_code": "<referral_code>"
    },
    "name": "claim_referral_code_api_referrals_claim_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
referral_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the mutation's key side effect (10 credits to both claimer and referrer), but it omits permissions, error cases, idempotency, and whether a code can only be claimed once.

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?

The core purpose and reward are front-loaded in two short sentences. The trailing Responses section is boilerplate that adds little value, and the title repeats the first sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter mutation, the description covers the primary action and reward. However, with no annotations and no output schema, it should clarify authentication/prerequisites and what the successful response actually returns.

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

Parameters2/5

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

There is one required parameter with 0% schema description coverage. The description restates the concept of a referral code but adds no format, source, or validation details beyond the parameter name.

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 states a precise verb+resource ("Claim a referral code") and adds the concrete effect of awarding 10 credits to both parties. This distinguishes it from the sibling get_referral_code, although it does not explicitly name alternatives.

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 intended use is implied by the phrase "Claim a referral code" and the credit award, but there is no explicit when-to-use guidance, prerequisites, or comparison to alternatives such as get_referral_code.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HopeHire toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources