Galatic.ai

Share library item

share_gallery_item

Share one of the user's library items to the public community feed (share true, the default) or take it back (share false). Shared items are visible to anyone without signing in, prompt included, under displayName (default "Anonymous"); the userId is not shown. Returns { sharedAt } when shared; 404 for an item that is not the caller's. id comes from list_gallery or search. Use delete_gallery_item to remove an item entirely.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "share_gallery_item"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Item id from list_gallery or search.
`share`	No	true shares, false unshares.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`displayName`	No	Name shown on the shared item. Defaults to "Anonymous".
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 27, 2026
- addedInput schema / properties / displayName / description
```
Added value: +"Name shown on the shared item. Defaults to \"Anonymous\"."
```
- addedInput schema / properties / id / description
```
Added value: +"Item id from list_gallery or search."
```
- addedInput schema / properties / share / description
```
Added value: +"true shares, false unshares."
```
First observedOct 24, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the real consequence: the item and its prompt become visible to anyone without signing in, displayName defaults to 'Anonymous', and the userId is not exposed. It also documents the return value ({ sharedAt }) and the 404 failure mode for items the caller doesn't own. It stops short of stating whether sharing is reversible in-place or whether there are rate limits, and does not clarify that repeated share=true calls are effectively idempotent despite idempotentHint=false.

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?

Three dense sentences, front-loaded with the action and polarity, then effects, then return/error contract, then sibling routing. No sentence is removable — each carries a distinct behavioral fact.

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 6-parameter mutation tool with no output schema, the description supplies what the schema cannot: publication semantics, the anonymous-display default, ownership-based 404 behavior, and the return shape. The three required analytics parameters are fully specified in the schema, so the description need not repeat them.

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?

Schema coverage is 100%, so the baseline is 3; the description adds genuine meaning on top by explaining the visibility consequence of displayName ('name shown on the shared item' vs. the userId never being shown) and restating the true/false polarity of share. It says nothing about the required analytics params (context, llm_model, conversation_id), but those are thoroughly documented in the schema.

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 ('Share one of the user's library items to the public community feed') plus the inverse operation ('take it back'), and explicitly contrasts with the sibling delete_gallery_item. An agent can distinguish share vs. unshare vs. delete without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the exact condition for each mode (share true = publish, share false = unshare) and names the alternative when the goal is removal: 'Use delete_gallery_item to remove an item entirely.' This is an explicit routing rule to a sibling, not an inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Galatic.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.