Skip to main content
Glama
Sign In
mcp-karyawan

mcp-karyawan

by michaeltio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_karyawan

Retrieve an employee's data by their unique ID. Returns employee details or an error if the ID does not exist.

Instructions

Ambil data satu karyawan berdasarkan id. Gagal jika id tidak ditemukan.

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": {
      "id": "<id>"
    },
    "name": "get_karyawan"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that the tool fails if the id is not found, providing error behavior. Additional details like read-only nature are implicit but acceptable.

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 two sentences with no redundant information. It is front-loaded with the primary action and includes the error condition concisely.

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?

Given the low complexity (one parameter, single resource) and presence of an output schema, the description covers purpose and error behavior. It is complete enough for an agent to select and invoke correctly, though slightly more detail on the id would help.

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?

The description does not elaborate on the 'id' parameter beyond its existence. With 0% schema coverage, it fails to add meaning such as format, example, or source, despite the parameter being self-explanatory.

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 'Ambil' (retrieve) and resource 'data satu karyawan' (data of one employee), clearly distinguishing it from sibling tools like list_karyawan (multiple records) and update/delete/create (mutations).

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?

The description states it retrieves data based on id, implying usage when a specific id is known. It does not explicitly list when not to use or provide alternatives, but the context is clear enough.

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

Deploy Server

Other Tools