Skip to main content
Glama

Japanese company profile

get_company_profile
Read-onlyIdempotent

One profile for a Japanese corporation from its 13-digit corporate number: registered name and address, invoice (tax) registration status, and listing, industry and capital if it files with EDINET.

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": {
      "corporate_number": "<corporate_number>"
    },
    "name": "get_company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
corporate_numberYes13-digit corporate number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond them: the data provenance is EDINET filings, and listing/industry/capital are only present 'if it files with EDINET', warning the agent that some fields may be absent. It stops short of saying what happens for an unknown or malformed corporate number.

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?

One front-loaded sentence with no filler: the key, the resource, and the returned fields in a single pass. Nothing repeats the title or wastes tokens.

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?

With no output schema, the description carries the return-value burden and does so by naming the fields, plus flagging the EDINET-conditional ones. It is nearly complete for a one-parameter read tool; only error/not-found behavior is unaddressed.

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?

There is a single parameter with 100% schema description coverage that already states '13-digit corporate number', and the description merely restates the same constraint. It adds no format, validation, or normalization guidance (e.g. whether hyphens are accepted), so the schema is doing all the work.

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-and-resource pair (retrieve one Japanese corporation's profile) keyed by a 13-digit corporate number, and enumerates the returned fields: registered name/address, invoice registration status, listing, industry, capital. This is enough to distinguish it from search_company and search_listed_companies, which return sets rather than a single profile.

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?

Usage is only implied: the tool needs a 13-digit corporate number, which suggests it is a lookup-by-identifier step rather than a search. It never says where to obtain that number or that search_company should be called first when the agent only has a company name, leaving the selection path to inference.

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.

Resources