Skip to main content
Glama

MCP OAuth client-interop conformance

Claim the free trial month

claim_trial

claim the one-time free first Solo month for your first server (the POST /trial/claim operation; Bearer token required; EIP-191 proof required — first call the REST POST /trial/challenge, sign the returned message with your registered wallet, then pass nonce + signature here, exactly as REST)

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

Input Schema

NameRequiredDescriptionDefault
checkNo
nonceNosingle-use nonce from POST /trial/challenge
walletNooptional; must equal the account's registered payer wallet
clientsNo
idp_shapeNo
signatureNoEIP-191 personal_sign signature of the challenge message by the claimed wallet
apply_shimsNo
full_matrixNo
server_nameNo
server_configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / check
      Added value: +{
      +  "type": "object"
      +}
    • addedInput schema / properties / nonce
      Added value: +{
      +  "description": "single-use nonce from POST /trial/challenge",
      +  "type": "string"
      +}
    • addedInput schema / properties / signature
      Added value: +{
      +  "description": "EIP-191 personal_sign signature of the challenge message by the claimed wallet",
      +  "type": "string"
      +}
    • addedInput schema / properties / wallet
      Added value: +{
      +  "description": "optional; must equal the account's registered payer wallet",
      +  "type": "string"
      +}
  2. Changed5 schema fields changed
    • addedInput schema / properties / apply_shims
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / clients
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / full_matrix
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / idp_shape
      Added value: +{
      +  "enum": [
      +    "dcr_friendly",
      +    "cognito_like",
      +    "strict_loopback"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / server_config
      Added value: +{
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the materially important behavior that this is a one-time grant requiring an out-of-band EIP-191 challenge/signature exchange. It omits what happens on success or repeat claims and whether the trial can be revoked, which keeps it below a 5.

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?

One sentence, front-loaded with the purpose, with the auth procedure packed efficiently into a parenthetical. Dense but every clause carries information; the nesting makes it harder to scan than a short bulleted flow would.

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

Completeness2/5

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

For a 10-parameter mutation tool with nested objects, an enum, no output schema, and 0 required parameters, the description covers only the auth path. An agent still has no basis for setting server_config, idp_shape, apply_shims, full_matrix, or check, which is a substantial completeness gap.

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?

Schema coverage is only 30% across 10 parameters. The description clarifies the auth trio (nonce, signature, wallet) and the challenge-message flow, but leaves check, clients, idp_shape, apply_shims, full_matrix, server_name, and server_config completely unexplained in both schema and description — including nested objects and an enum that an agent cannot safely populate.

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 precise verb and resource: claim the one-time free first Solo month for the first server, and identifies it as the POST /trial/claim operation. That is enough for an agent to distinguish it from subscribe_solo and subscription_status without opening any schema.

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?

Gives explicit preconditions and ordering: Bearer token required, first call POST /trial/challenge, sign the returned message with the registered wallet, then pass nonce + signature here. It does not explicitly say when to prefer this over subscribe_solo, so it stops short of full when/when-not guidance.

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