Skip to main content
Glama

Search Companies

search_companies
Read-onlyIdempotent

Search film companies by company name, CEO, or category code, then retrieve each company's company_cd for detailed company information.

Instructions

영화사(제작사, 배급사 등)를 검색합니다. 결과의 company_cd 로 get_company_info 를 호출할 수 있습니다.

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": "search_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo페이지 번호 (1부터)
ceo_nameNo대표자명
per_pageNo페이지당 결과 수 (최대 100)
part_codeNo영화사 분류 코드 (get_code_list 로 조회)
company_nameNo영화사명

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds one useful behavioral fact beyond that: results carry a company_cd that links to get_company_info. It says nothing about pagination limits, result ordering, or how many pages are typically available, so the addition is real but modest.

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?

Two short sentences with zero filler, and the core purpose is front-loaded before the follow-up chaining tip. Nothing is repeated from the schema or annotations.

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 a full output schema, complete parameter coverage, and rich annotations, the description does not need to explain return values or safety. It is nearly complete for a simple optional-filter search, with only minor gaps around pagination behavior and how to interpret a large result set.

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%: all five parameters (page, per_page, ceo_name, part_code, company_name) carry their own descriptions including defaults and bounds. The description adds no meaning beyond the schema and mentions company_cd, which is an output field rather than an input, so the baseline 3 applies.

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 names a specific verb and resource ('영화사(제작사, 배급사 등)를 검색합니다') and clarifies the scope of the resource by listing production and distribution companies. It is immediately clear what the tool does, but it does not explicitly distinguish itself from sibling searches such as search_movies or search_people, which is what a 5 would require.

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 second sentence tells the agent what to do after a successful call (feed company_cd into get_company_info), which is a genuine chaining hint. However, it gives no guidance on when to use this search versus calling get_company_info directly, and no guidance on how to combine the optional filters.

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