Skip to main content
Glama
beylessai

Hiworks Mail MCP

read_username

Retrieve a username from the Hiworks Mail system to enable email operations such as searching, reading, and sending messages with attachments.

Instructions

하이웍스 username을 읽어옵니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameNo
passwordNo

Implementation Reference

  • The handler function for the 'read_username' tool. It takes username and password as input and returns them as a JSON string in the MCP response format.
    async ({ username, password }) => {
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify({
              username: username,
              password: password
            })
          }
        ]
      };
    }
  • src/index.ts:136-153 (registration)
    Registration of the 'read_username' tool using server.tool, including the description, schema reference (emailSchema), and inline handler.
    server.tool(
      'read_username',
      '하이웍스 username을 읽어옵니다.',
      emailSchema,
      async ({ username, password }) => {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                username: username,
                password: password
              })
            }
          ]
        };
      }
    );
  • Zod schema used for input validation of the 'read_username' tool (shared with other email tools).
    const emailSchema = {
      username: z.string().default(process.env['HIWORKS_USERNAME'] || ''),
      password: z.string().default(process.env['HIWORKS_PASSWORD'] || '')
    };
  • Tool schema declaration in the MCP server capabilities section.
    read_username: {
      description: '하이웍스 username을 읽어옵니다.',
      parameters: {
        type: 'object',
        properties: {
          username: { type: 'string' },
          password: { type: 'string' }
        },
        required: ['username', 'password']
      }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation but doesn't disclose authentication needs (despite username/password parameters), rate limits, error conditions, or what the return value looks like. This is inadequate for a tool with parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's appropriately sized for a simple tool, though it could be more informative without sacrificing brevity.

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

Completeness2/5

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

For a tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It doesn't explain parameter usage, return values, or behavioral context, making it incomplete for effective agent use.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate but doesn't mention parameters at all. The two parameters (username, password) are undocumented in both schema and description, leaving their purpose and usage unclear. The description adds no value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '하이웍스 username을 읽어옵니다' (Reads Hiworks username) states a clear verb+resource action, but it's somewhat vague about what exactly is being read. It doesn't distinguish from sibling tools like read_email or search_email, leaving ambiguity about whether this reads a specific user's username or lists usernames.

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 guidance is provided on when to use this tool versus alternatives like read_email or search_email. The description doesn't mention prerequisites, context, or exclusions, leaving the agent with no usage direction beyond the basic purpose.

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/beylessai/hiworks-mcp'

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