Skip to main content
Glama
primadonna-gpters

AgentSkills MCP Server

by primadonna-gpters
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

business_data

Retrieve Korean company information, news, and financial data by name or business registration number for business research purposes.

Instructions

Look up Korean business data including company information, news, and financial data. Useful for researching Korean companies by name or business registration number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesType of data to retrieve: 'company-info', 'news', or 'financial'
companyNameNoCompany name in Korean or English (e.g., '삼성전자', 'Samsung Electronics')
businessNumberNoKorean business registration number (사업자등록번호). Optional alternative to companyName.

Implementation Reference

  • src/index.ts:196-215 (handler)
    The handler logic for the business_data tool, which constructs the request body and calls the internal API.
    case "business_data": {
  const { type, companyName, businessNumber } = args as {
    type: string;
    companyName?: string;
    businessNumber?: string;
  };

  const body: Record<string, unknown> = { type };
  if (companyName) body.companyName = companyName;
  if (businessNumber) body.businessNumber = businessNumber;

  const result = await callApi("/api/skills/business-data", body);

  return {
    content: [
      {
        type: "text",
        text: JSON.stringify(result, null, 2),
      },
    ],
  • src/index.ts:116-137 (registration)
    Registration and schema definition for the business_data tool.
    name: "business_data",
description:
  "Look up Korean business data including company information, news, and financial data. " +
  "Useful for researching Korean companies by name or business registration number.",
inputSchema: {
  type: "object",
  properties: {
    type: {
      type: "string",
      description:
        "Type of data to retrieve: 'company-info', 'news', or 'financial'",
      enum: ["company-info", "news", "financial"],
    },
    companyName: {
      type: "string",
      description: "Company name in Korean or English (e.g., '삼성전자', 'Samsung Electronics')",
    },
    businessNumber: {
      type: "string",
      description:
        "Korean business registration number (사업자등록번호). Optional alternative to companyName.",
    },

Tool Definition Quality

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It identifies the operation as 'look up' (read-only implication) and data types retrieved, but omits critical operational details: error behavior when companies aren't found, data freshness/recency, rate limits, or whether results are structured vs. plain text.

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?

Two sentences efficiently structured: capability declaration followed by use case. No redundancy or filler content, though the second sentence partially overlaps with the schema's explicit mentioning of identification methods.

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?

Adequate for a 3-parameter lookup tool with complete schema coverage. However, lacking both annotations and output schema, the description should ideally disclose return value structure or empty-result behavior. As written, it leaves the agent uncertain about response format.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline applies. The description mirrors the schema content (mapping enum values to data types and noting the identification alternatives) but does not add syntactic constraints, validation rules, or interaction logic beyond what the schema already documents.

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?

Clear verb 'Look up' and specific resource 'Korean business data' with enumerated subtypes (company info, news, financial). However, it lacks explicit differentiation from sibling 'web_search', which could also retrieve company information, leaving the agent to infer the specialization from 'Korean' context.

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?

States the tool is 'Useful for researching Korean companies' and identifies the two lookup methods (name or registration number), providing implied context. However, it lacks explicit 'when-not-to-use' guidance or comparison to 'web_search' alternative, leaving ambiguity about when this specialized tool is preferred over general search.

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/primadonna-gpters/agentskills-mcp'

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