Skip to main content
Glama

Handoff: Send Files to Users & Agents

Create an account

signup

Create a Handoff account and return an API key once. No Authorization header is required. Save api_key. On later calls send Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass api_key only if you cannot set headers. share_file can create this key for you. The key is a secret. Do not put it in a file you share.

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

Input Schema

NameRequiredDescriptionDefault
refNoOptional attribution label. Lowercase letters, digits, dot, underscore, or hyphen. At most 64 characters.
agent_idNoOptional label, unique across Handoff. Letters, numbers, underscore, and hyphen.

Output Schema

NameRequiredDescriptionDefault
capsYes
nextYes
api_keyYes
agent_idYes
account_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ref
      Added value: +{
      +  "description": "Optional attribution label. Lowercase letters, digits, dot, underscore, or hyphen. At most 64 characters.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "pattern": "^[a-z0-9._-]+$",
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "account_id": {
      +      "type": "string"
      +    },
      +    "agent_id": {
      +      "type": "string"
      +    },
      +    "api_key": {
      +      "type": "string"
      +    },
      +    "caps": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "file_mb": {
      +          "type": "number"
      +        },
      +        "files": {
      +          "type": "number"
      +        },
      +        "opens_per_day": {
      +          "type": "number"
      +        },
      +        "total_mb": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "total_mb",
      +        "files",
      +        "opens_per_day",
      +        "file_mb"
      +      ],
      +      "type": "object"
      +    },
      +    "next": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "configs": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "claude_code": {
      +              "type": "string"
      +            },
      +            "cursor_json": {
      +              "additionalProperties": false,
      +              "properties": {
      +                "mcpServers": {
      +                  "additionalProperties": false,
      +                  "properties": {
      +                    "handoff": {
      +                      "additionalProperties": false,
      +                      "properties": {
      +                        "headers": {
      +                          "additionalProperties": false,
      +                          "properties": {
      +                            "Authorization": {
      +                              "type": "string"
      +                            }
      +                          },
      +                          "required": [
      +                            "Authorization"
      +                          ],
      +                          "type": "object"
      +                        },
      +                        "url": {
      +                          "type": "string"
      +                        }
      +                      },
      +                      "required": [
      +                        "url",
      +                        "headers"
      +                      ],
      +                      "type": "object"
      +                    }
      +                  },
      +                  "required": [
      +                    "handoff"
      +                  ],
      +                  "type": "object"
      +                }
      +              },
      +              "required": [
      +                "mcpServers"
      +              ],
      +              "type": "object"
      +            }
      +          },
      +          "required": [
      +            "claude_code",
      +            "cursor_json"
      +          ],
      +          "type": "object"
      +        },
      +        "first_call": {
      +          "type": "string"
      +        },
      +        "header": {
      +          "type": "string"
      +        },
      +        "if_no_headers": {
      +          "type": "string"
      +        },
      +        "mcp_url": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "header",
      +        "mcp_url",
      +        "if_no_headers",
      +        "configs",
      +        "first_call"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "account_id",
      +    "api_key",
      +    "agent_id",
      +    "caps",
      +    "next"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say it is a non-idempotent, non-destructive write; the description adds the crucial behaviors: the key is returned exactly once, it cannot be retrieved later, no auth is needed to call it, and three accepted header forms exist for subsequent calls. It also flags the key as a secret that must not be placed in shared files — material guidance annotations do not carry.

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?

Purpose and one-time key return are front-loaded, and the auth/secret guidance is dense but each sentence carries operational value. Slightly list-like, and the stray api_key parameter note is the one sentence that does not earn its place here.

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

Completeness5/5

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

Output schema exists, so return values need not be spelled out, yet the description still flags the one-time nature of the key — the single fact an agent must not miss. Auth requirements, secret handling, and the sibling alternative are all covered; nothing needed to call it correctly is missing.

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?

Schema coverage is 100% and both parameters (ref, agent_id) are fully documented in the schema, so the baseline is 3. The description adds nothing about them and instead mentions an api_key parameter that does not exist in this schema, a minor source of confusion rather than added meaning.

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 specific verb and resource ("Create a Handoff account") plus the distinctive outcome ("return an API key once"), which is exactly what separates it from the share/file siblings. An agent can tell what this does without opening the 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 real routing context: no Authorization header is required for this call, and "share_file can create this key for you" names an alternative path. The note "Pass api_key only if you cannot set headers" is confusing because api_key is not a parameter of this tool, which keeps it from a 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.