View all glossaries in your account to enforce specific terminology during translation.
Lists all glossaries in your Lara Translate account. Glossaries are collections of terms with their translations that enforce specific terminology during translation.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Glossaries accessible to the authenticated account |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.4Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "items": {
+ "description": "Glossaries accessible to the authenticated account",
+ "items": {
+ "additionalProperties": {},
+ "properties": {
+ "createdAt": {
+ "description": "ISO 8601 timestamp",
+ "type": "string"
+ },
+ "id": {
+ "description": "Unique glossary identifier (format: gls_*)",
+ "type": "string"
+ },
+ "isPersonal": {
+ "description": "True if the glossary is private to the owner",
+ "type": "boolean"
+ },
+ "name": {
+ "description": "Display name of the glossary",
+ "type": "string"
+ },
+ "ownerId": {
+ "description": "Identifier of the glossary owner",
+ "type": "string"
+ },
+ "updatedAt": {
+ "description": "ISO 8601 timestamp",
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "ownerId",
+ "createdAt",
+ "updatedAt",
+ "isPersonal"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "items"
+ ],
+ "type": "object"
+}v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds that it lists all glossaries and explains their purpose, but does not disclose potential behavioral traits such as pagination, limits, or ordering. With annotations present, the description provides minor additional context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is perfectly concise with no unnecessary words. It efficiently communicates the purpose and the nature of glossaries.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple listing tool with no parameters and an existing output schema, the description is largely complete. It could be improved by mentioning whether pagination or limits apply, but overall it provides sufficient context for an agent to understand what the tool does.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the schema coverage is 100%. The description adds value by explaining what a glossary is, which is relevant context for the returned data. Given no parameters, a baseline of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool lists all glossaries in the user's account, with a brief explanation of what glossaries are. It distinctively separates from sibling tools like get_glossary (single item) and create_glossary (creation).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no explicit guidance on when to use this tool over alternatives like get_glossary or the many other sibling tools. The usage context is implied but not stated, e.g., for obtaining an overview before selecting a specific glossary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/translated/lara-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server