Skip to main content
Glama

Call card state

call_card_state
Read-only

Call card only: the call's status, transcript, open questions, takeover and recording in one read, by call_id or by the number a place tool is still dialing.

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

Input Schema

NameRequiredDescriptionDefault
toNoInstead of call_id: the live call to this number placed in the last two minutes.
call_idNo
card_idNo

Output Schema

NameRequiredDescriptionDefault
toYes
call_idYes
outcomeYes
takeoverYes
lifecycleYes
recipientYes
timestampsYes
transcriptYes
delegationsYes
talk_secondsYes
outcome_titleYes
recording_srcYes
audio_availableYes
phone_takeover_availableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / card_id
      Added value: +{
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / delegations / items / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / delegations / items / properties / replies / items / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / takeover / anyOf
      Previous value: -[
      -  {
      -    "oneOf": [
      -      {
      -        "additionalProperties": false,
      -        "properties": {
      -          "at": {
      -            "type": "string"
      -          },
      -          "state": {
      -            "const": "ringing",
      -            "type": "string"
      -          },
      -          "via": {
      -            "const": "phone",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "via",
      -          "state",
      -          "at"
      -        ],
      -        "type": "object"
      -      },
      -      {
      -        "additionalProperties": false,
      -        "properties": {
      -          "at": {
      -            "type": "string"
      -          },
      -          "state": {
      -            "const": "connected",
      -            "type": "string"
      -          },
      -          "via": {
      -            "enum": [
      -              "phone",
      -              "browser"
      -            ],
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "via",
      -          "state",
      -          "at"
      -        ],
      -        "type": "object"
      -      },
      -      {
      -        "additionalProperties": false,
      -        "properties": {
      -          "at": {
      -            "type": "string"
      -          },
      -          "state": {
      -            "const": "unanswered",
      -            "type": "string"
      -          },
      -          "via": {
      -            "const": "phone",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "via",
      -          "state",
      -          "at"
      -        ],
      -        "type": "object"
      -      }
      -    ]
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "oneOf": [
      +      {
      +        "additionalProperties": {},
      +        "properties": {
      +          "at": {
      +            "type": "string"
      +          },
      +          "state": {
      +            "const": "ringing",
      +            "type": "string"
      +          },
      +          "via": {
      +            "const": "phone",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "via",
      +          "state",
      +          "at"
      +        ],
      +        "type": "object"
      +      },
      +      {
      +        "additionalProperties": {},
      +        "properties": {
      +          "at": {
      +            "type": "string"
      +          },
      +          "state": {
      +            "const": "connected",
      +            "type": "string"
      +          },
      +          "via": {
      +            "enum": [
      +              "phone",
      +              "browser"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "via",
      +          "state",
      +          "at"
      +        ],
      +        "type": "object"
      +      },
      +      {
      +        "additionalProperties": {},
      +        "properties": {
      +          "at": {
      +            "type": "string"
      +          },
      +          "state": {
      +            "const": "unanswered",
      +            "type": "string"
      +          },
      +          "via": {
      +            "const": "phone",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "via",
      +          "state",
      +          "at"
      +        ],
      +        "type": "object"
      +      }
      +    ]
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / timestamps / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / transcript / items / additionalProperties
      Previous value: -falseNew value: +{}
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add context. It usefully says the read bundles five distinct data categories and that `to` targets a number a place tool is still dialing, but it does not say what happens if no live call is found, if multiple identifiers are supplied, or what precedence applies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words; the scope marker leads and the identifier options follow. It is dense to the point of being slightly cryptic ('Call card only'), but nothing is redundant.

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?

An output schema exists, so the description needn't enumerate return values, and it correctly summarizes the payload categories instead. The remaining gap is the lack of any rule for choosing among the three optional, non-required identifiers, which matters for correct invocation.

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 only 33% (call_id and card_id have no descriptions), so the description must compensate. It explains the call_id-versus-number tradeoff and gives the `to` parameter real meaning ('the number a place tool is still dialing'), but card_id is never mentioned anywhere, leaving one of three parameters undocumented in both schema and description.

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 the resource precisely ('the call's status, transcript, open questions, takeover and recording in one read') and scopes it with 'Call card only', which distinguishes it from narrower siblings like get_call or get_call_transcript. The verb is implicit ('in one read') rather than stated, but an agent can tell what the tool returns without opening the schema.

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?

'Call card only' hints at an exclusion, and the phrase 'the number a place tool is still dialing' implies a use case for in-flight calls. However, it never states when to choose this over get_call, get_call_transcript, or the call_card_action sibling, so routing must be inferred from the listed contents rather than from explicit guidance.

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.