Slither MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get_function_callers

Find all functions that call a specific function, categorized by type. Use for dead code detection and refactoring impact analysis.

Instructions

Gets all functions that call a specific function (incoming edges in the call graph). Use this when finding entry points to a function, understanding usage patterns, or assessing impact of changes. Returns categorized callers: internal, external, and library. Useful for dead code detection and refactoring impact analysis.

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": {
      "request": "<request>"
    },
    "name": "get_function_callers"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`callers`	No
`success`	Yes
`error_message`	No
`query_context`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.3.2Jul 13, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses return categories (internal, external, library) and general use cases, but lacks details on limitations (e.g., recursion, analysis requirements). Adequate but not exhaustive.

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?

Two concise sentences plus a short phrase about usefulness. No wasted words, front-loaded with core purpose.

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?

With an output schema present and no annotations, the description explains purpose and return categorization well. Could mention prerequisites or error conditions, but overall complete for agent to use correctly.

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?

Tool description does not cover parameters (schema coverage 0%), but the input schema itself has thorough descriptions for path, function_key, and include_query_context. Baseline 3 is appropriate as agent can rely on schema.

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 clearly states the tool gets all functions that call a specific function, with specific use cases (entry points, usage patterns, impact). It distinguishes from siblings like get_function_callees by focusing on incoming edges.

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?

Explicitly says when to use it (finding entry points, understanding usage, impact assessment, dead code detection, refactoring). Could improve by noting when not to use or comparing to alternatives, but current context is sufficient.

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