Skip to main content
Glama

Jaryo - Korean company records, sourced. Start with verify_company (no key)

Get a company profile

get_company
Read-only

Company profile by Jaryo id: names (ko/en), all identifiers, current profile records (DART overview, procurement vendor profile, tax status, pension headcount) and record counts. Every value carries its source and license. Requires a Jaryo API key.

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_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJaryo entity id (26-char ULID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds credit beyond that: it discloses that every value is source- and license-attributed and that an API key is required, which tells the agent about auth and provenance behavior not encoded in annotations. It does not discuss pagination, rate limits, or behavior for missing records, keeping it below a 5.

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 dense sentences, front-loaded with the resource and followed by the returned payload contents and the auth requirement. Every clause carries information, though the parenthetical record listing is slightly heavy and could be trimmed without loss.

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?

For a single read-only getter with no output schema, the description is largely complete: it names the identifier type, the returned profile groupings, provenance guarantees, and the API key prerequisite. Missing only a note on what happens when the id is unknown or access is unauthorized, which would matter for a real call.

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 coverage is 100% and the single id parameter is already documented as a 26-char ULID in the schema. The description repeats 'by Jaryo id' but adds no format, resolution, or error-handling semantics beyond the schema. Baseline 3 is appropriate when the schema fully documents the only parameter.

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?

States a specific verb+resource (company profile by Jaryo id) and enumerates exactly what it returns: names in ko/en, all identifiers, current profile records (DART overview, vendor profile, tax status, pension headcount) and record counts. That level of specificity distinguishes it from list_company_records (lists records) and search_companies (search) without naming them.

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 lookup is clearly implied to be an id-based single-entity fetch, and the 'Requires a Jaryo API key' line gives an operational prerequisite. But there is no explicit when-to-use vs alternatives (e.g. resolve_company to get an id, search_companies to find one, list_company_records for history), which this sibling set would make valuable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.