Skip to main content
Glama

Dutify

by ai.dutify.mcp
OverviewDiscussionsAdmin

hub_get_call

Read-onlyIdempotent

Fetch a single call by ID. Returns the full UserCallDTO. Field map (the DTO is deeply nested):

  • top-level id (integer) — what /usercall/{id} expects, what list/search return

  • top-level clickupList/jiraProjectId/airtableBaseId/airtableTableId — populated when this call has been pushed to that vendor

  • top-level summaryApplied/actionItemsApplied/etc. (bool) — has the summary/etc. been pushed?

  • call.id (integer) — INTERNAL Zoom/Meet/Teams call id, NOT for /usercall/{id} paths

  • call.callUuid (string) — what hub_send_call_to_jira/clickup/airtable want as callUUID

  • call.attendees (string, often "") — NOT a structured array

  • call.recordings[i].id (integer) — recording id for /recording/{id}/audio-url etc.

  • call.recordings[i].summary/keyPoints/actionItems/enhancedNotes — markdown STRINGS, not arrays; the CALLER's own version (generated from their workspace prompt, per-call prompt, notes and note template), never another participant's

  • call.recordings[i].userNotes — only the caller's own desktop notes, null otherwise Requires recordings:read scope.

Input Schema

NameRequiredDescriptionDefault
idYesUserCall integer ID — the OUTER `id` from list/search/etc., NOT the inner `call.id`.
accountNoMulti-account auth only: name of the account from X-Dutify-Accounts to use for this call. Ignored in single-account mode (X-API-Key header). When multiple accounts are configured and this is omitted, the call fails with ACCOUNT_REQUIRED listing the available names. list_accounts never requires a selection.
workspaceNoWorkspace identifier or exact name for this call. Overrides the configured workspace. For personal keys, discover candidates with list_workspaces and select explicitly. Does not change other calls or expand a workspace key's access.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it names the returned DTO, maps nested fields to their meanings and intended API use, clarifies that summary fields are markdown strings rather than arrays, notes that userNotes are caller-only, and states the required recordings:read scope. This is especially valuable because there is no output schema.

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?

The description is front-loaded with the core action and then uses a structured field map for the nested DTO. Despite its length, every bullet earns its place because the return shape is complex and there is no output schema to document it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the deeply nested UserCallDTO and the absence of an output schema, the description provides the field interpretation an agent needs to use the result correctly. It also covers the authorization scope, making the definition complete for this retrieval 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 description coverage is 100%, so the id, account, and workspace parameters are already documented in the schema. The description reinforces that the tool takes a call ID, but it does not add new parameter-level guidance beyond what the schema already provides; its detail is focused on returned fields.

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?

The description opens with a specific verb and resource: fetching a single call by ID, returning the full UserCallDTO. It clearly distinguishes retrieval-by-ID from list/search siblings through the ID-based framing and provides a detailed field map of what will be returned.

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

Usage Guidelines4/5

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

It clearly establishes that this tool is used when retrieving one call by its ID and states the required recordings:read scope. It does not explicitly compare against alternatives like hub_search_calls or hub_list_calls, but the context is sufficiently clear for an agent to select the right tool when an ID is available.

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

All Dutify toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources