Skip to main content
Glama

Keep paths open on a private app

appSharingSetOpenPaths
Idempotent

Choose up to 10 exact paths of a private app that runs on a server, which other services like webhooks can still reach. Anyone can reach these paths. Requires confirmed: true, representing the human’s agreement.

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>",
      "paths": "<paths>",
      "confirmed": "<confirmed>"
    },
    "name": "appSharingSetOpenPaths"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes
confirmedYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
stateYes
messageYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds genuinely useful context beyond them: the hard cap of 10 paths, the security consequence that anyone can reach these paths, and the human-confirmation gate. It does not say whether existing open paths are replaced or merged, which is the key behavioral question for a 'set' operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and scope, followed by the security consequence and the confirmation requirement. The reachability idea is stated twice ('which other services like webhooks can still reach' then 'Anyone can reach these paths'), which is a mild redundancy but serves to escalate the warning.

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?

An output schema exists, so return values need not be described, and annotations cover the safety/idempotency profile. The remaining gaps are the unmentioned projectId parameter and the unspecified replace-vs-append semantics; both are notable but the description is otherwise adequate for a 3-parameter mutation.

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?

Schema description coverage is 0% across 3 parameters, so the description must compensate. It explains 'paths' (exact paths, up to 10) and 'confirmed' (must be true, means the human agreed), covering two of three, but 'projectId' — required and UUID-formatted — is never mentioned, leaving the agent to infer which app the paths apply to.

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?

States a concrete resource and scope: up to 10 exact paths of a private app that must remain reachable by other services such as webhooks. The verb 'Choose' is softer than 'set/replace', leaving slight ambiguity about whether the list is replaced or extended, but the resource and effect are clear enough to distinguish it from siblings like appSharingSetMode or appSharingAddPeople.

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 webhook reachability framing implies the use case (opening specific endpoints of a private app), and it states a hard prerequisite (confirmed: true reflecting human agreement). It gives no explicit when-not guidance and does not name an alternative tool for related sharing operations, so routing between siblings is left to inference.

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