Skip to main content
Glama

Read who can open an app

appSharingGet
Read-onlyIdempotent

Read who can open one of your apps (anyone with the link, only people you choose, or anyone with an access code), with the link to share, the people on the list and the current code. This is about opening the app at all, not its own sign-up (appUsersSetSignupMode).

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": {
      "projectId": "<projectId>"
    },
    "name": "appSharingGet"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
codeYes
edgeYes
laneYes
linkYes
modeYes
peopleYes
messageYes
removalYes
wentLiveYes
availableYes
openPathsYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that by specifying exactly what facets of access are reported (link, people list, current code) and by drawing the boundary against sign-up configuration, which prevents an agent from conflating two distinct access concepts.

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 sentences, zero filler: the capability and its return content come first, and the disambiguation against appUsersSetSignupMode comes second. Nothing is repeated from the title or annotations and every clause carries information.

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?

For a single-parameter read-only tool with an output schema already describing the returned access settings, the description covers purpose, scope, and the sign-up boundary. The only residual gap is what projectId means and any authorization prerequisite, which is minor at this complexity level.

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?

There is one parameter with 0% schema description coverage, so the schema does nothing to explain projectId. The description only implies it via "one of your apps"; it never says that projectId is the app identifier or how to obtain it. The parameter is a conventional UUID app reference, which softens the gap, but the description adds no explicit semantics.

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?

The description names a specific verb and resource ("Read who can open one of your apps") and enumerates the concrete modes it reports (anyone with the link, chosen people, access code) plus the payload (link, people list, code). This is enough to distinguish it from the sibling mutators without opening a schema.

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 explicitly bounds the tool's scope: "This is about opening the app at all, not its own sign-up (appUsersSetSignupMode)", pointing at the sibling that handles the adjacent concern. It never explicitly contrasts with the write-side siblings (appSharingSetMode, appSharingSetOpenPaths), so the when-to-use is clear but the when-not is only partially covered.

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