Skip to main content
Glama

Invite by email

share_invite

Invite a person by email to an artifact you own (owner only); they get the same invite mail as from the Share panel. Call this only when the user asks you to invite that person; never invite anyone or grant access on your own. role is view, comment or edit. expiresAt (optional, ISO 8601 in the future) ends their access at that time. Subject to the mail quota (rate_limited). Returns { id, email, role, inviteId, expiresAt? }.

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": {
      "id": "<id>",
      "email": "<email>",
      "role": "<role>"
    },
    "name": "share_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
roleYes
emailYes
expiresAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the supplied annotations: it discloses the owner-only authorization requirement, that an email is actually dispatched (same mail as the Share panel), that the call is subject to a mail quota and can return rate_limited, and exactly what the response contains. The annotations only say readOnly=false and destructive=false, so this added authorization, side-effect, and failure-mode context is genuinely valuable.

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?

Front-loads the action and scope, then layers the usage restriction, parameter meanings, and return shape in short declarative sentences. Every sentence adds information the agent cannot get from the schema or annotations, and there is no filler.

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 4-parameter mutation tool with no output schema, the definition covers permissions, side effects, rate limiting, parameter formats, and the exact return shape, which is everything needed to invoke it correctly and interpret the result.

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?

With 0% schema description coverage the description carries the burden and mostly does: role is given as view/comment/edit, expiresAt is explained as optional ISO 8601 in the future that ends access, and email is stated to be the invitee's address. The id parameter is only implicitly identified as the artifact (via 'artifact you own') rather than explicitly, leaving a small gap.

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 ('Invite a person by email to an artifact') plus the ownership scope ('owner only'), which immediately separates it from link-based or listing siblings such as share_link and share_list.

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 an explicit trigger condition ('Call this only when the user asks you to invite that person') and an explicit prohibition ('never invite anyone or grant access on your own'), which is unusually strong guidance. It stops short of naming alternatives (e.g., share_link for link-based access or share_role for changing an existing member's role), so the routing picture is clear but not exhaustive.

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