Skip to main content
Glama

Get Company Info

get_company_info
Read-onlyIdempotent

Retrieve detailed film company information, including representative, category, and filmography, by company code from search results.

Instructions

영화사 상세 정보(대표자, 분류, 필모그래피 등)를 조회합니다.

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

Input Schema

NameRequiredDescriptionDefault
company_cdYes영화사 코드 (search_companies 결과의 company_cd)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds only a brief indication of the returned content (representative, category, filmography), and says nothing about failure behavior for an invalid or unknown company code.

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?

A single short sentence that front-loads the action and the resource with zero redundant wording. Nothing in it is filler or repetition of the title alone.

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 one-parameter read tool with full annotation coverage and an output schema (so return shape needn't be explained), the definition is largely sufficient. The remaining gap is that it does not state what happens with an invalid code or how it relates to search_companies, which would help an agent choose correctly.

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, and the schema already explains that company_cd comes from search_companies results, so the schema carries the semantic load. The description does not mention company_cd at all and adds no format or sourcing detail beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb ('조회합니다' / retrieve) and resource (영화사 상세 정보 / movie company detail), and enumerates the kinds of fields returned (대표자, 분류, 필모그래피). It does not explicitly contrast itself with the sibling search_companies, so an agent must infer that this is the detail-fetch counterpart to that search tool.

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

Usage Guidelines2/5

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

The description contains no when-to-use or when-not-to-use guidance and never names search_companies as the alternative for finding companies. The only routing hint ('company_cd from search_companies results') lives in the input schema, not in the description, so the definition itself leaves usage entirely implicit.

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