Skip to main content
Glama

List keys with suggestions

list_keys_with_suggestions
Read-only

List keys that have pending (active) translation suggestions in a language. Returns up to 100 keys per page; use list_suggestions on a key to see the suggestions themselves.

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

Input Schema

NameRequiredDescriptionDefault
pageNoOptional: page number (0-based, default 0)
branchNoOptional: branch name
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

A4.2/5.0
Behavior4/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 safety is covered; the description adds the useful behavioral facts that only 'active' suggestions count and that results are capped at 100 keys per page. It does not state ordering or what happens past the last page, which are minor remaining gaps given the annotation coverage.

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 sentences, no filler, with the scope and the 100-per-page limit front-loaded and the alternative tool named last. Every clause carries information an agent needs.

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?

For a read-only paginated list tool with fully described parameters and annotations covering safety, the description supplies what is needed to call it correctly, including the page cap and the follow-up path. The only omission is what identifying fields each returned key carries, which is a modest gap for a tool with no output schema.

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 page, branch, projectId and languageTag are already documented in the schema. The description only echoes that results are language-scoped and paginated, adding no new syntax or constraint detail beyond the structured fields — the baseline 3 for full schema coverage 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?

The description uses a specific verb and resource ('List keys that have pending (active) translation suggestions') and adds the language scoping, which cleanly separates it from list_keys (all keys) and list_suggestions (suggestions for one key). An agent can pick it 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 Guidelines4/5

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

It gives a clear use condition — find keys that have pending suggestions — and names the follow-up tool ('use list_suggestions on a key to see the suggestions themselves'), which is genuine routing guidance. It stops short of explicitly stating when NOT to use it (e.g., when you want all keys regardless of suggestions, use list_keys), so it is strong but not exhaustive.

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.