Skip to main content
Glama

get_language

Retrieve the current language settings of your Gmail account.

Instructions

Gets language settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:853-862 (registration)
    Registration of the 'get_language' tool via server.tool(), which defines the tool name, description, schema (no params), and the handler function.
    server.tool("get_language",
      "Gets language settings",
      {},
      async () => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.getLanguage({ userId: 'me' })
          return formatResponse(data)
        })
      }
    )
  • The handler (async callback) that executes the tool logic: calls gmail.users.settings.getLanguage({ userId: 'me' }) and formats the response.
      async () => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.getLanguage({ userId: 'me' })
          return formatResponse(data)
        })
      }
    )
  • The input schema for get_language: an empty object (no parameters) as defined by the third argument to server.tool().
    server.tool("get_language",
      "Gets language settings",
      {},
Behavior3/5

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

No annotations are present, so the description must convey behavioral traits. It states 'Gets' which implies a read-only, non-destructive operation. However, it lacks confirmation of no side effects, authorization needs, or any rate limits. The transparency is adequate but minimal.

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?

The description is extremely concise—only three words—with no redundant information. Every word is necessary, and it is front-loaded with the core purpose. No waste.

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?

For a simple tool with no parameters, no output schema, and no annotations, the description is minimally complete. It tells the agent what the tool does, but could be improved by specifying the scope (e.g., current user's language settings). Given the abundance of sibling get tools, more context would help.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, and the schema description coverage is 100% (vacuously). The description adds no extra meaning beyond the schema, but baseline for 0 parameters is 4, as no parameter documentation is needed.

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 'Gets language settings' clearly identifies the action (gets) and resource (language settings). It is specific enough to distinguish from other get tools like get_profile or get_vacation, but does not elaborate on which language settings are targeted, which could be ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No usage guidelines are provided. The description does not mention when to use this tool versus alternatives such as update_language, nor does it specify context like prerequisites or typical scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shinzo-labs/gmail-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server