Skip to main content
Glama
Sign In

Vivere

by dev.vivere
OverviewDiscussionsAdmin

Share page

share_page
Idempotent

Share one of your pages with the account of a person who has a Vivere login (email) or with one of your teams (team_id), as viewer or editor, or change the role they have. Needs a free seat for anybody new.

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": {
      "page_id": "<page_id>",
      "role": "<role>"
    },
    "name": "share_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesviewer sees status and history; editor can also add, change and delete monitors and route their alerts
emailNoThe person's login email
page_idYesPage id
team_idNoOr a team id, from list_teams

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations' mutation, idempotency, and non-destructive signals, it discloses two useful prerequisites: an individual recipient must already have a Vivere login, and anybody new requires a free seat. It does not explain failure behavior when those prerequisites fail or whether recipients are notified.

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?

Two compact sentences front-load the operation, recipient options, roles, and role-update capability, followed by the seat constraint. There is no redundant explanation of schema details, though the first sentence is fairly dense.

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

Completeness4/5

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

Together with the fully described schema and annotations, this provides enough context to select the tool and usually invoke it correctly. The main remaining gap is recipient-parameter cardinality, with minor omissions around error behavior and alternatives for access removal.

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?

Although schema coverage is 100%, the description adds that the email must belong to an existing Vivere login, that the team must be one of the caller's teams, and that new recipients consume a seat. However, the wording only implies a choice between email and team_id; it does not explicitly define exactly-one, both, or neither handling.

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 clearly identifies the action and resource: sharing a page with a person or team, assigning viewer/editor access, or changing an existing role. These details distinguish the access-management operation in general terms, but it does not explicitly contrast itself with siblings for revoking or privatizing access.

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?

It gives concrete use contexts: share using a Vivere login email or one of the caller's teams, and reuse the operation to change an existing role. It lacks explicit when-not guidance or an alternative for removing access.

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

All Vivere toolsInspect
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.

Resources