Skip to main content
Glama
jgottlieb84

agentline-mcp

by jgottlieb84

get_call

Retrieve call status, transcript, and summary after initiating a call. Poll until terminal status (completed, failed, no_answer, busy) is reached.

Instructions

Get status, transcript, and summary for a call. Call this after make_call to check whether the call has completed. Terminal statuses are completed, failed, no_answer, busy — anything else means the call is still in progress and you should poll again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
call_idYes

Implementation Reference

  • The get_call tool handler function. Takes a call_id string, calls the Agentline SDK's get_call method, and returns the result as a dict. This is the core implementation of the 'get_call' MCP tool.
    @mcp.tool()
    def get_call(call_id: str) -> dict:
        """Get status, transcript, and summary for a call. Call this after
        `make_call` to check whether the call has completed. Terminal statuses are
        `completed`, `failed`, `no_answer`, `busy` — anything else means the call
        is still in progress and you should poll again.
        """
        try:
            result = _client_or_init().get_call(call_id)
            return asdict(result)
        except AgentlineError as e:
            return {"error": str(e), "status_code": e.status_code}
  • The @mcp.tool() decorator registers get_call as an MCP tool on the FastMCP instance named 'mcp'.
    @mcp.tool()
Behavior4/5

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

No annotations provided; description discloses read-like behavior and polling need, but could clarify idempotency and auth requirements.

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 concise sentences, each serving a distinct purpose: purpose, usage timing, and status details.

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?

Adequate for a simple polling tool; lists returned fields and usage context, but no output schema to supplement return format details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter call_id has 0% schema description coverage and description provides no additional meaning beyond the schema's title.

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?

Description clearly states it retrieves status, transcript, and summary for a call, distinguishing it from siblings like make_call and hangup_call.

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

Usage Guidelines5/5

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

Explicitly instructs to call after make_call to check completion, lists terminal statuses, and implies polling for non-terminal states.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jgottlieb84/agentline-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server