SAGOT

calls_list

List calls, newest first. Status refused = an incoming call SAGOT didn't answer: refusal says why ({code, message, fix}), what the caller experienced (handling: rang_through = the phone kept ringing for a person, hung_up, message_played = a short notice) and how often it repeated within 10 minutes (repeats). Refused calls cost nothing and don't count as calls in usage. A queued call canceled before dialing carries the same refusal.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspaceId": "<workspaceId>"
    },
    "name": "calls_list"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`workspaceId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

C2.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and adds meaningful context: newest-first ordering, semantics of refused calls, refusal structure, handling modes, repeat counts, zero cost, and queued-call cancellation behavior. It does not mention pagination, permissions, or rate limits, but it discloses substantial domain behavior beyond the schema.

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?

The description is front-loaded with the core purpose and then explains refused-call semantics in a structured way. It is somewhat dense but every sentence adds useful domain information rather than repeating the schema.

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

Completeness2/5

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

There is no output schema, and the description only partially explains return values by detailing refused-call fields. It does not explain the three input parameters, pagination behavior, or the general shape of non-refused call records, leaving important context missing for a paginated list tool.

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

Parameters1/5

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

The input schema has 0% description coverage and three parameters, but the description never explains workspaceId, limit, or cursor. It describes returned call fields instead of input parameters, so it does not compensate for the schema gap.

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 clearly states a specific verb and resource: "List calls, newest first." It distinguishes the tool by its ordering behavior, though it does not explicitly contrast with sibling tools such as calls_get or platform_calls_list.

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

Usage Guidelines2/5

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

The description explains the meaning of refused calls but gives no guidance on when to use this tool instead of alternatives like calls_get or platform_calls_list. It also does not mention prerequisites, filtering options, or exclusions.

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

All SAGOT tools Inspect

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

Need Help?