Skip to main content
Glama

buggy_functions

Lists functions in a Python file with signatures and flags which are investigable, so you can inspect unfamiliar files or find why a function cannot be analyzed.

Instructions

List the functions in a Python file with their signatures, and say which can be investigated. Call this first when you do not know what is in a file, or when a function turns out not to be investigable and you need the reason.

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": {
      "file": "<file>"
    },
    "name": "buggy_functions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to the Python file, absolute or relative to cwd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full disclosure burden. It usefully reveals the return content (signatures plus an investigability verdict and reason), but says nothing about behavior on missing files, non-Python input, or how the investigability verdict is determined.

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 sentences, both earning their place: the first defines the output, the second defines when to reach for it. Nothing is repeated from the name or schema.

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 no output schema, the description must convey what comes back, and it does so at a high level (functions, signatures, investigability, reason). The exact shape of that output and edge-case handling are left unstated, but the essentials for calling it correctly are present.

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 100% and the single 'file' parameter is already documented with path semantics in the schema. The description adds no meaning beyond that, so the baseline of 3 for well-covered schemas applies.

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 states a specific verb and resource ('List the functions in a Python file with their signatures') and adds the distinguishing extra output ('say which can be investigated'). An agent can tell this apart from buggy_investigate or buggy_scan without opening either schema.

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 gives a concrete triggering condition: call this first when you don't know what's in a file, or when a function turns out not to be investigable and you need the reason. It does not name the alternative tools or state when-not to use it, which keeps it just short of the top mark.

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