Skip to main content
Glama

Search Japanese companies

search_company
Read-onlyIdempotent

Search all ~5.8 million corporations registered in Japan by name (Japanese, partial match). Returns corporate number, address, type and whether it is closed. Use the corporate number with get_company_profile.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCompany name or part of it, in Japanese, e.g. トヨタ自動車
limitNo
prefectureNoOptional prefecture filter in Japanese, e.g. 大阪府
include_closedNoInclude closed corporations (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/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 the safety profile is fully covered by structured data. The description adds the result shape (corporate number, address, type, closed flag) and notes that closed firms are only returned on request, which is useful. Beyond that it says nothing about result caps, ranking, or what an empty result means, so it only modestly exceeds the annotation baseline.

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?

Three short sentences, zero filler, with the searchable corpus size and match semantics front-loaded before the return fields and the follow-up hint. Every clause carries information an agent can act on.

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, listing the returned fields is exactly the right move, and the pointer to get_company_profile completes the workflow. The main residual gap is pagination and the limit parameter's effect, which neither the description nor the schema explains, leaving result-set handling slightly under-specified for a 5.8-million-row corpus.

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 75% and the description's parameter-relevant content ('by name, Japanese, partial match') largely restates the schema's own name description. The limit and include_closed parameters get no elaboration in the description, and the prefecture filter is only covered by the schema. Baseline 3 is appropriate when the schema does most of 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 ('Search all ~5.8 million corporations registered in Japan by name'), including the matching mode (Japanese, partial match) and the scope of the corpus. It also names the natural follow-up tool, get_company_profile, so an agent can separate this lookup from profile retrieval without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear usage context: name-based lookup over the Japanese corporate registry, with the Japanese-language requirement and partial-match behaviour spelled out. It also hands off to get_company_profile for detail retrieval. It does not, however, distinguish this from similarly-named siblings such as search_listed_companies or search_address, so the agent must infer which registry to query.

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