Skip to main content
Glama

extend_share

Idempotent

Change when an active share expires, for example to give a late recipient more time. The link and key stay the same. It can last at most the plan's longest expiry from the day it was sent (Free 7, Pro 30, Studio 90, Business 365 days); a later date answers expiry_too_long.

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": {
      "share_id": "<share_id>",
      "expires_at": "<expires_at>"
    },
    "name": "extend_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_idYesThe share's id (uuid).
expires_atYesThe new expiry, RFC 3339 (e.g. 2026-10-12T17:00:00Z): at least an hour away, at most the plan's longest expiry from the day the share was sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds real context beyond the annotations: the link and key stay the same (no re-distribution needed), the plan-tier maximum expiry window is spelled out with concrete day counts, and the failure mode expiry_too_long is named. That is exactly the operational knowledge an agent needs before calling a mutation.

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?

Three tight sentences, front-loaded with the action, then the invariant, then the constraint and error. No wasted words.

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 two-parameter mutation with no output schema, the definition covers the invariant, the limit, and the error path. Nothing an agent needs to invoke it correctly is missing.

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. The description still adds value by tying expires_at to plan limits and naming the resulting error, though it doesn't expand on share_id beyond the schema's uuid note.

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 (change the expiry of an active share) and scopes it precisely. Clearly distinct from siblings like revoke_share or get_share, which act on a different aspect of the same object.

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?

The example ('give a late recipient more time') gives a concrete use case, and 'active share' implies the prerequisite state. It does not explicitly exclude alternatives (e.g. revoke and re-create), so it stops short of 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.

Resources