Skip to main content
Glama
Sign In

SuprSend

by com.suprsend
OverviewDiscussionsAdmin

List translations

translations_list
Read-onlyIdempotent

Lists the translation files of the workspace (one per locale and namespace), which templates use to show text in the user's language. Use translations_get for the keys.

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": {
      "workspace": "<workspace>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "translations_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNolive (default): the published files. draft: with unpublished changes.live
limitNoItems per page (1–100).
offsetNoItems to skip (the paging note of the previous page gives it).
contextYesAnalytics: why you call this tool, in 10-20 words. Say "a user", never names, emails, or IDs.
llm_modelYesAnalytics: your model ID, or "unknown".
workspaceYesThe slug of the workspace to act on. Call workspaces_list to find the valid values.
conversation_idNoPass 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.

Output Schema

NameRequiredDescriptionDefault
metaYes
resultsYes
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds useful structural context (results are one entry per locale+namespace pair) but says nothing about pagination behavior or what a returned file contains, which is the remaining behavioral gap for a list tool.

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 short sentences with zero filler; the resource granularity is front-loaded and the sibling routing follows immediately. Nothing is repeated from the schema or annotations.

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 read-only paginated list with a full output schema and complete annotation coverage, the description supplies everything an agent needs: what is listed, at what granularity, and where to go for key-level data. Return values need not be restated because an output schema exists.

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%, so mode/limit/offset/workspace semantics are fully documented in the schema itself. The description adds no parameter-level detail beyond implicitly scoping to the workspace, so the baseline of 3 applies.

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 ('Lists') and resource ('translation files of the workspace') and clarifies the granularity — one file per locale and namespace — which distinguishes it from sibling listing tools. It also explicitly routes key-level detail to translations_get rather than leaving that to inference.

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 names the alternative tool and the condition that selects it ('Use translations_get for the keys'), giving clear routing guidance. It does not state when not to use this tool at all (e.g. if you only need one locale), but the primary alternative is covered.

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

All SuprSend toolsInspect
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.

Resources