Skip to main content
Glama

List suggestions

list_suggestions
Read-only

List translation suggestions for a key in one language. Returns up to 100 results per page.

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": {
      "keyName": "<keyName>",
      "languageTag": "<languageTag>"
    },
    "name": "list_suggestions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional: page number (0-based, default 0)
branchNoOptional: branch name
statesNoOptional: only suggestions in these states (ACTIVE, ACCEPTED, DECLINED). Default: all.
keyNameYesThe translation key name
namespaceNoOptional: namespace of the key
projectIdNoID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
languageTagYesLanguage tag (e.g. 'de')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact – a hard cap of 100 results per page – but says nothing about ordering, what a suggestion record contains, or how the default state filter behaves.

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, zero filler, with the resource and scope front-loaded and the pagination constraint immediately after. Nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, no output schema, and a read-only list operation, the definition is minimally adequate because the schema carries all parameter detail. However, with no output schema the description should say more about what a suggestion record looks like or how results are ordered, and it omits any mention of the default state filter's practical effect.

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 every parameter including page, branch, states, namespace and projectId is already documented in the schema. The description adds no syntax, format, or interaction detail beyond the page-size limit, so the baseline 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?

States a specific verb and resource ("List translation suggestions") plus the scoping dimensions (a key, one language), which separates it from siblings like list_keys_with_suggestions and accept_suggestion/decline_suggestion. It stops short of explicitly naming an alternative, but the scope is unambiguous.

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?

Usage is only implied by the phrase "for a key in one language" – the agent can infer this is the read path for suggestions on a specific key. There is no explicit when-to-use/when-not guidance, no mention of how it relates to list_keys_with_suggestions, and no note that accept/decline are separate tools.

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.