Skip to main content
Glama
Sign In
mcp-karyawan

mcp-karyawan

by michaeltio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_karyawan

Update specific fields of an employee record by ID. Fields set to None are left unchanged.

Instructions

Perbarui data karyawan berdasarkan id. Field bernilai None tidak diubah.

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": "update_karyawan"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
namaNo
emailNo
statusNo
jabatanNo
departemenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that fields with value None are not changed, which is important behavioral information. However, it does not mention other aspects like authorization requirements or return behavior.

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 only two sentences, concise and front-loaded with the core action and key behavioral note. Every sentence adds value without redundancy.

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?

The description covers the core behavior (update by id, None fields unchanged) but lacks detail on parameter usage, return values, or prerequisites. Given 6 parameters and an output schema exists (unseen), more context could improve completeness for an AI agent.

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 add meaning. It only explains the id parameter implicitly and the behavior for None fields. For 6 parameters, this is insufficient to clarify the semantics of nama, email, status, jabatan, and departemen beyond their names.

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 clearly states the action 'Perbarui' (update), the resource 'data karyawan' (employee data), and the key identifier 'berdasarkan id' (by id). It effectively distinguishes this tool from sibling tools like create, list, get, and delete.

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?

The description implies when to use the tool (to update employee data by id) but does not explicitly mention when not to use it or provide alternatives. Sibling tools are listed but not referenced, offering no guidance on selection.

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