Handoff: Send Files to Users & Agents

Update share expiry

update_share

Set when an owned share expires. expires_in_hours is measured from now. Example: 168 for 7 days. Does not return the token. Requires your API key.

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": {
      "grant_id": "<grant_id>",
      "expires_in_hours": "<expires_in_hours>"
    },
    "name": "update_share"
  }
}

Input Schema

Name	Required	Description
`api_key`	No	Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you share.
`grant_id`	Yes
`expires_in_hours`	Yes

Output Schema

Name	Required	Description	Default
`status`	Yes
`file_id`	Yes
`audience`	Yes
`grant_id`	Yes
`max_opens`	Yes
`expires_at`	Yes
`open_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (not read-only, not destructive, not idempotent), so the description does not need to repeat those. It usefully adds that the expiry is measured from now, that the token is not returned, and that an API key is required; it does not explain what happens if the new expiry is earlier than the current one or what the maximum bound means in practice.

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?

The description is four short sentences, front-loaded with the action and followed by the most useful parameter detail. Nothing is padded or redundant.

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

Completeness3/5

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

The output schema and annotations already carry return shape and safety, so the description only needs to close parameter and auth gaps. It does that for expires_in_hours but leaves the required grant_id undefined and gives no guidance on the effect of moving an expiry earlier.

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 only 33%, so the description has to compensate. It explains expires_in_hours well (relative to now, 168 means 7 days), but grant_id is never described anywhere, and the example does not mention the schema's 87600-hour maximum.

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 first sentence gives a specific verb and target: setting the expiry time of an owned share. That is enough to distinguish it from creation or revocation in spirit, but the description never names or contrasts the closest siblings such as revoke_share or get_share_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the tool is for shares you own and gives one example, but it does not state when not to use it or point to alternatives for removing access or checking status. The agent must infer the boundaries from the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Handoff: Send Files to Users & Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.