제품
통합데모 예약
지금 전화하세요:(800) 931-5930
Capterra Reviews

제품

  • Pass
  • 데이터 인텔리전스
  • WMS
  • YMS
  • 배송
  • RMS
  • OMS
  • PIM
  • 부기
  • 트랜로드

통합

  • B2C 및 전자상거래
  • B2B 및 옴니채널
  • 기업
  • 생산성 및 마케팅
  • 배송 및 주문 처리

리소스

  • 가격
  • IEEPA 관세 환불 계산기
  • 다운로드
  • 도움말 센터
  • 산업
  • 보안
  • 이벤트
  • 블로그
  • 사이트맵
  • 데모 예약
  • 문의하기

뉴스레터를 구독하세요.

제품 업데이트 및 뉴스를 받아보세요. 받은 편지함. 스팸이 없습니다.

ItemItem
개인정보 보호정책약관 서비스데이터 보호

저작권 항목, LLC 2026 . All Rights Reserved

SOC for Service OrganizationsSOC for Service Organizations

    Function Calling: CubeworkFreight & Logistics Glossary Term Definition

    HomeGlossaryPrevious: Responsible ClassifierFunction CallingLLM integrationAI toolsAPI interactionAgent developmentNatural Language
    See all terms

    What is Function Calling?

    Function Calling

    Definition

    Function Calling is a capability within Large Language Models (LLMs) that allows the model to determine when and how to call external functions or APIs based on a user's natural language request. Instead of generating a direct answer, the LLM outputs a structured JSON object specifying the function name and the required arguments.

    Why It Matters

    LLMs, in their base form, are knowledge engines, not action engines. Function Calling bridges this gap. It allows the abstract reasoning power of the LLM to be connected to the concrete, real-world capabilities of external systems, such as databases, weather services, or booking platforms. This transforms a conversational AI into an actionable agent.

    How It Works

    1. Tool Definition: Developers provide the LLM with a schema (a description of the available functions, their parameters, and what they do). This is the 'tool definition'.
    2. User Prompt: The user provides a request (e.g., "What is the weather in London?").
    3. Model Inference: The LLM analyzes the prompt against the provided tool definitions and determines that the get_weather function is appropriate.
    4. Function Call Output: The LLM does not execute the code; it returns a structured call request (e.g., {"name": "get_weather", "arguments": {"location": "London"}}).
    5. Execution & Response: The application hosting the LLM receives this structured call, executes the actual external API call (e.g., to OpenWeatherMap), and passes the result back to the LLM.
    6. Final Response: The LLM uses the returned data to formulate a natural language answer for the user.

    Common Use Cases

    • Data Retrieval: Querying internal company databases or CRMs based on conversational input.
    • Task Automation: Booking appointments, sending emails, or updating records via external services.
    • Real-Time Information: Fetching live stock prices, flight statuses, or current weather conditions.
    • Complex Workflows: Orchestrating multi-step processes that require sequential API calls.

    Key Benefits

    • Extensibility: Dramatically expands the LLM's functional scope beyond its training data.
    • Accuracy & Grounding: Ensures answers are based on current, verifiable external data rather than potentially outdated internal knowledge.
    • Actionability: Moves AI from being purely informational to being operational.

    Challenges

    • Schema Management: Maintaining accurate and comprehensive tool definitions is crucial for reliable performance.
    • Latency: The multi-step process (Prompt -> Call -> Execute -> Response) introduces additional latency compared to a single model inference.
    • Error Handling: Robust logic must be implemented to gracefully handle failures from external APIs.

    Related Concepts

    • Agents: Function Calling is a core enabling technology for building autonomous AI agents.
    • Tool Use: A broader term encompassing the ability of an AI to utilize external resources.
    • Prompt Engineering: Designing the initial system prompt to correctly instruct the model on when and how to use the provided tools.

    Keywords