Skip to main content
Glama

Search keys

search_keys
Read-only

Search for translation keys in a Tolgee project by name or translation text. Returns up to 50 matching keys per page. Note: namespace and tags filtering is not yet supported — filter results client-side if needed.

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": {
      "query": "<query>"
    },
    "name": "search_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional: page number (0-based, default 0)
queryYesSearch query (matches key name or translation text)
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.
languageTagNoOptional: language tag to search translations in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectId / description
      Previous value: -"ID of the project (required for PAT, auto-resolved for PAK)"New value: +"ID 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."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavior the annotations do not: a hard cap of 50 results per page and the disclosure that namespace/tags filtering is unimplemented, which prevents failed expectations. It omits any mention of total counts or pagination termination, so not a 5.

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 sentences, front-loaded with the purpose, followed by the result-size bound and the limitation caveat. No sentence is redundant and nothing is buried.

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?

With no output schema, the description carries the burden of describing returns; it covers the page size but not whether pagination metadata or total counts come back. For a read-only search with five well-documented parameters, that is a minor gap rather than a blocking one.

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 the schema already explains page, query, branch, and languageTag. The description adds little parameter-level meaning beyond restating that the query matches key name or translation text; the 50-per-page cap is the only semantic detail the schema lacks, and it is stated globally rather than tied to the page parameter.

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?

The description gives a specific verb and resource ("Search for translation keys in a Tolgee project") and scopes the match to key name or translation text. It implicitly distinguishes itself from enumeration tools like list_keys, but never names the closest sibling alternatives, so it stops short of a 5.

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?

It usefully rules out namespace and tag filtering and suggests filtering client-side, which is real exclusion guidance. However, it gives no explicit trigger for choosing this over list_keys or get_key, and no prerequisites for narrowing by branch or languageTag beyond the schema.

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.