Skip to main content
Glama

Split the Tab

Get a host setup link

get_host_handoff_link

Get a fresh hostHandoffUrl for a bill you created, so the host can finish setup on their phone. Only the key that created the bill can do this. Never ask for or accept a Venmo or Zelle handle. The host adds it on their phone through the handoff link. Keep assistantKey inside tool calls and never show it to the user. Give the user hostHandoffUrl.

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": {
      "bill": "<bill>",
      "assistantKey": "<assistantKey>"
    },
    "name": "get_host_handoff_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
billYesA Split the Tab bill link (https://…/b/<id>) or the bill id.
assistantKeyYesThe assistantKey returned when you created or joined this bill. Pass it on every later call for this bill.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses an authorization constraint (creator key only), a security constraint (`assistantKey` must stay inside tool calls and never be shown to the user), and an output-handling instruction (hand `hostHandoffUrl` to the user). The 'fresh' framing also implies a newly minted token, consistent with readOnlyHint=false. This is unusually rich behavioral context for a two-parameter 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?

Five short sentences, front-loaded with what the tool returns and why, followed by the authorization, safety, secrecy, and handoff instructions. Every sentence carries an operational instruction; no filler or restatement of the title.

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?

For a simple two-parameter, no-output-schema tool with annotations covering the safety profile, nothing material is missing. Purpose, authorization, secret handling, and the value to surface to the user are all covered.

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 100%, so the baseline is 3, but the description adds real meaning: the `bill` must be one you created, and `assistantKey` is a secret that belongs only in tool calls. That goes beyond the schema's own wording about passing the key on later calls.

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 gives a specific verb and resource: fetch a fresh `hostHandoffUrl` for a bill the caller created, with the stated goal that the host finishes setup on their phone. That is far more precise than a tautology. It does not, however, reference any sibling tool (get_bill, edit_bill, etc.), so an agent must infer the boundary from names alone.

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?

Use context is clearly implied: call this when the host needs to complete setup, and only for a bill you created ('Only the key that created the bill can do this'). It also tells the agent what not to do procedurally (never ask for or accept a Venmo or Zelle handle). It stops short of explicitly excluding alternative tools or stating failure behavior for non-creator keys.

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