Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

get_agent_links

Read-only

List an agent's specialist-transfer links, in try order — where this agent hands a live call off to another agent in the workspace.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_agent_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeNoRequired on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
agent_idYesagent UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, non-open-world operation. Beyond that, the description adds meaningful behavioral context by saying the links are returned in try order and by defining them as call-handoff targets in the workspace.

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 definition is a single sentence with no wasted wording. It front-loads the operation and then adds the essential domain meaning of the links.

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?

For a simple read-only list tool with no output schema, the description gives enough semantic context to call the tool correctly and understand what the returned links represent. It could be slightly more complete by explicitly mentioning the setter alternative or any expected return shape, but no critical information is missing.

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 agent_id and purpose parameters are already documented in the input schema. The description does not add syntax, format, or usage details beyond what the schema provides, so a baseline score is appropriate.

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 uses a specific verb, resource, and scope: it lists an agent's specialist-transfer links in try order. It also explains that these links represent live-call handoff destinations, which distinguishes this tool from sibling tools like set_agent_links and list_agent_tools.

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 makes the read-only inspection use case clear from context, especially through the phrase 'where this agent hands a live call off.' However, it does not explicitly state when to use this tool versus set_agent_links or other agent-related listing tools, so usage guidance is implied rather than complete.

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

All Sautikit 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