Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List calls behind call intelligence

luca_analytics_call_intelligence_calls
Read-onlyIdempotent

Fetch recent completed calls with coach summaries, attendance, ratings, and lead names; optionally scope results by workspace ID or slug.

Instructions

Most recent completed calls with a generated summary, newest first: the coach-facing summary, attendance outcome, rating, and lead name.

Luca operation: GET /api/analytics/call-intelligence/calls Required scopes: analytics:read Required OAuth scope: luca:read; data sensitivity: full_content Does not require idempotency. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered; the description goes further by disclosing required scopes (analytics:read, luca:read), data sensitivity (full_content), the completed-with-summary filter, and newest-first ordering. This is useful behavioral context beyond the structured fields.

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?

Front-loaded with the resource and scope in the first sentence, followed by compact metadata lines. Efficient overall, though the boilerplate operation/idempotency lines are somewhat mechanical rather than decision-relevant.

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 return values need not be spelled out, and the description covers scopes, sensitivity, ordering, and workspace override. The only real gap is the undocumented limit semantics, otherwise it is complete enough for a read-only listing tool.

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 coverage is 67%, with workspaceId/workspaceSlug already documented in the schema, and the description usefully explains the override intent ('override the default workspace configured by environment'). However the limit parameter (1–50, no default stated) is left undescribed in both schema and text, so it does not fully compensate.

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 (List) and resource (calls behind call intelligence) and further narrows scope to 'most recent completed calls with a generated summary, newest first,' even naming the returned fields. That is clear enough for an agent to know what it retrieves, though it never contrasts itself with the related luca_analytics_call_intelligence or the call_events_* siblings.

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?

The description implies when to use it (to surface recent, summarized, completed calls) and gives workspace-override guidance, but offers no explicit when-not or alternatives despite a very crowded sibling set of call/analytics tools. Usage is inferable but not routed.

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

Deploy Server

Other Tools