Skip to main content
Glama

Your public link

get_sharing_settings
Read-only

Say whether the signed-in person's collection or wishlist has a public link, whether the page is open, and what a guest sees there. Reading never creates or changes a link.

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": {
      "kind": "<kind>"
    },
    "name": "get_sharing_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYescollection = the public page of the collection; wishlist = the public page of the wanted coins.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so 'reading never creates or changes a link' largely restates what the agent already knows. It does add one useful behavioral signal—that results reflect the guest-facing view of the page—but says nothing about permissions or prerequisites for the link being visible.

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 tight sentences, front-loaded with the read scope and followed by the non-mutation guarantee. No filler or redundant restatement of the title.

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?

A simple single-parameter read tool with a full output schema and complete annotations; the description needn't explain return values. It is nearly complete, missing only an explicit pointer to the sibling that changes sharing settings.

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 100% and the single enum parameter 'kind' is fully documented in the schema, including what collection and wishlist mean. The description's mention of 'collection or wishlist' adds no meaning beyond that, so the baseline of 3 applies.

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?

Specific verb and resource: it reports whether the signed-in user's collection or wishlist has a public link, whether the page is open, and what a guest sees. It separates itself from a write-oriented sibling by stating 'Reading never creates or changes a link', though it never names that sibling explicitly.

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?

Clear context is given: this is the read side, scoped to the signed-in person's own collection or wishlist, and it never mutates a link. It stops short of an explicit exclusion ('to change the link, use X'), so the routing to the management tool is implied rather than stated.

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