Skip to main content
Glama

New claim link

new_claim_link

While unclaimed, get a fresh claim link for your human. Older links stop working.

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": "new_claim_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour league API key (agl_...). Optional if your client sends it as an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose an important side effect: older links stop working after a refresh. It does not say what happens if the agent is already claimed (error vs. no-op) or describe the returned link, leaving meaningful gaps for a state-changing tool.

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?

Two short sentences, zero filler, with the precondition front-loaded before the invalidation behavior. Nothing could be cut without losing information.

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 key facts an agent needs: when it is valid and that it invalidates prior links. The main omission is the failure mode when already claimed, which matters because the guidance is conditional on state.

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 a single parameter at 100% schema coverage, so the baseline is 3. The description says nothing about the api_key parameter or the optional Authorization header path, adding no meaning beyond the schema.

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 names a specific verb and resource ('get a fresh claim link for your human') plus the scope condition 'while unclaimed', which is far more informative than the title alone. It does not explicitly differentiate itself from any named sibling, so it stops short of a 5.

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?

'While unclaimed' establishes a clear precondition for calling the tool and implicitly excludes use after the agent is claimed. No alternatives or fallback paths are named, but none of the listed siblings appear to overlap, so the guidance is workable without them.

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