Skip to main content
Glama

List shared access

share_list

List who has access to an artifact you own (owner only): { id, url, linkRole, members: [{ email, name?, role, via? ("link" for people who joined by link), expiresAt? }], invites: [{ inviteId, email, role, expiresAt, accessExpiresAt? }] }. Tokens are never returned.

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>"
    },
    "name": "share_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

It goes beyond annotations by disclosing the owner-only authorization requirement and the security guarantee that tokens are never returned, which is real added context. However, annotations declare readOnlyHint=false for what is plainly a listing operation, and the description does not explain that discrepancy or what happens when the caller is not the owner (error vs empty).

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?

One sentence, front-loaded with the verb and scope, then the return shape and the token guarantee. No filler; every clause (owner-only, token non-exposure) carries information an agent needs.

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?

With no output schema, the inline description of the returned fields (id, url, linkRole, members, invites, expiresAt) is essential and present. The gaps are minor: no error behavior for non-owners and no explicit statement that the input id is the artifact id.

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?

Only one parameter with 0% schema description coverage, so the description must carry the meaning. Saying 'an artifact you own' implies the id is an artifact identifier, but it never states this explicitly nor the expected id format, leaving the single parameter only partially grounded.

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?

Names a specific verb and resource ('List who has access to an artifact') and constrains scope to artifacts the caller owns. It is clearly distinct from the mutation siblings (share_invite, share_remove, share_role), but it never explicitly contrasts itself with them or with share_link.

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?

The '(owner only)' qualifier gives an implicit precondition and the verb implies when to reach for it, but there is no explicit when-to-use/when-not guidance and no named alternative for non-owners or for link-management questions.

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