Skip to main content
Glama

claim_free_tier

Claim a member pass without paying while the free tier is open, for an account whose membership is not active, by a signature from that account (the message and the scheme per rail are in the terms under freeTier.howToClaim). The claim needs a signature, not funds. Configure Authorization: Bearer in your MCP client and omit the pass argument whenever headers are supported. The pass argument is a sensitive compatibility fallback for clients without header support. Arguments and credential-bearing results, including invoice, claim, free-tier claim and recovery results, may persist in client transcripts. Keep them private. A header takes precedence; conflicting credentials are refused.

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": {
      "account": "<account>",
      "timestamp": "<timestamp>",
      "signature": "<signature>"
    },
    "name": "claim_free_tier"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesa 0x address, a nano_ account or a base58 Solana address
signatureYes
timestampYesmilliseconds, the one signed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses the auth mechanism (Authorization: Bearer <pass>), the precedence rule (header wins, conflicting credentials refused), the sensitive nature of the pass fallback, and that credential-bearing results may persist in transcripts. These are precisely the behavioral traits annotations would otherwise have to supply.

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 claim action and its conditions are front-loaded, and each sentence adds distinct information (eligibility, auth, credential safety, precedence). It is dense and slightly long, but no sentence is clearly expendable.

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 credentialed claim operation with no annotations and no output schema, the description covers eligibility, authentication, credential precedence, and result sensitivity. It says little about failure modes (expired tier, already-claimed account) or what a successful result contains, leaving a modest gap.

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 67%, and the description adds real meaning beyond it: the signature must come from the claiming account, the message and scheme per rail are defined in freeTier.howToClaim, and the timestamp is 'the one signed'. It also discusses a `pass` argument that does not appear in the input schema, which introduces mild ambiguity about how that fallback is actually supplied.

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 specific verb and resource ('claim a member pass') plus the preconditions that qualify it: free tier open, membership not active, signature from that account. It does not explicitly contrast with sibling tools such as claim_invoice or free_tier, relying on the agent to infer the difference, which keeps it 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?

It clearly states when to use it (while the free tier is open, for an account whose membership is not active) and an important exclusion ('needs a signature, not funds'). It does not name an alternative tool or state when not to use this one, so 4 rather than 5.

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