Skip to main content
Glama
Sign In
jade-mcp

jade-mcp

by choiyounggi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

최근 신청 내역

jade_recent_applications
Read-only

Retrieve recent applications from the JADE main screen, including leave and attendance requests, with date, type, and approval status for quick status review.

Instructions

JADE 메인 화면에 보이는 최근 신청서(휴가·근태 등)의 일자·유형·결재 상태를 조회한다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jade_recent_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by naming the returned attributes and confirming this mirrors the main-screen widget rather than a full query. It does not say how many records 'recent' covers, whether there is a default limit, or what happens when there are no applications.

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?

A single compact sentence that leads with the resource and then the returned fields, with no filler. It could be marginally tighter, but nothing is redundant.

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?

With no output schema, the description bears responsibility for describing returns, and it does list the key fields. It omits record count, ordering, and empty-state behavior, and — most importantly for a family with a similarly named jade_applications — the scope boundary is left unspecified.

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?

The tool takes zero parameters, so the schema carries no semantic burden and the baseline is 4. The description correctly presents this as a no-argument call with no filtering options to explain.

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 gives a specific verb (조회한다) and resource (최근 신청서), and enumerates the fields returned (일자·유형·결재 상태) plus examples of application types (휴가·근태). However, it does not distinguish this from the sibling jade_applications, so an agent cannot tell the two apart from the text alone.

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 phrase 'JADE 메인 화면에 보이는' implies this returns only the short recent list surfaced on the home screen, which is an implicit scoping signal. There is no explicit when-to-use statement, no exclusion, and no pointer to jade_applications for broader or historical queries, so the agent must infer the split.

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