Galatic.ai

Community gallery

list_community

Read-onlyIdempotent

Browse public creations other users shared to the community gallery (showcase false, the default), or the showcase for one template category (showcase true). Community returns { items, nextKey, count }, newest first: limit up to 50 (default 20), type filters by media type, and nextKey goes back in as lastKey for the next page; category is ignored. Showcase needs category, returns { items, count } (up to 50, default 20) and ignores type and lastKey. Use list_gallery instead for the user's own library; share_gallery_item adds an item to the community feed. Read-only; creators' userIds are not 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "list_community"
  }
}

Input Schema

Name	Required	Description
`type`	No	Media type filter for the community feed. Ignored for showcase.
`limit`	No	Items per page; the server caps it at 50.
`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."
`lastKey`	No	nextKey from the previous community page. Ignored for showcase.
`category`	No	Template category id. Required for showcase, ignored otherwise.
`showcase`	No	true: one template category's showcase; false: the community feed.
`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.
`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.

Changed6 schema fields changedOct 26, 2026

addedInput schema / properties / category / description

Added value: +"Template category id. Required for showcase, ignored otherwise."

addedInput schema / properties / lastKey / description

Added value: +"nextKey from the previous community page. Ignored for showcase."

addedInput schema / properties / limit / description

Added value: +"Items per page; the server caps it at 50."

changedInput schema / properties / limit / minimum

Previous value: --9007199254740991New value: +1

addedInput schema / properties / showcase / description

Added value: +"true: one template category's showcase; false: the community feed."

addedInput schema / properties / type / description

Added value: +"Media type filter for the community feed. Ignored for showcase."

First observedOct 24, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is pre-declared. The description goes beyond by disclosing the return shapes per mode, the pagination loop (nextKey goes back in as lastKey), the 50-item server cap, and that creators' userIds are withheld — genuinely useful context. It stops short of describing ordering guarantees beyond 'newest first' or what nextKey absence means, keeping it out of the top band.

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?

Front-loads the core branching (community vs showcase) before pagination, returns, and sibling routing. Dense but waste-free; several sentences pack multiple clauses, which costs a point on scanability but not on content.

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?

No output schema exists, and the description compensates by enumerating both return shapes ({ items, nextKey, count } and { items, count }) and their ordering. The analytics-style params (context, llm_model, conversation_id) are fully documented in the schema, so nothing an agent needs to call this correctly is missing.

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 coverage is 100% and the schema already documents that type is ignored for showcase, category is required for showcase and ignored otherwise, and nextKey feeds lastKey. The description restates the same mode-parameter coupling and the limit cap rather than adding new semantics, so per the high-coverage baseline this is a 3 — the schema is doing the heavy lifting.

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 ('Browse public creations other users shared to the community gallery') and immediately distinguishes the two operating modes via the showcase flag. It also names the siblings it is not (list_gallery, share_gallery_item), so an agent can separate this from adjacent tools 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?

Explicit routing: use list_gallery for the user's own library, share_gallery_item to contribute to the feed, and this tool for the public feed or a single category's showcase. It also states the default (showcase false) so the agent knows the no-flag behavior.

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.