Skip to main content
Glama

buggy_scan

Scan every supported function in a Python file and return one line per function to triage unfamiliar code, with optional preconditions, postconditions, budget, and timeout controls.

Instructions

Investigate every supported function in a Python file and return one line per function. Use it to triage a file you are unfamiliar with. Note that any preconditions and postconditions apply to all functions alike, which is blunt; investigate individually for anything that matters.

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_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath to the Python file, absolute or relative to cwd.
budgetNoInputs to execute before giving up. Default 300.
timeoutNoSeconds allowed per call. Default 2.
preconditionsNoPreconditions as PYTHON expressions over the parameter names, e.g. 'budget > 0'. For an instance method the constructor's parameters are in scope too. Inputs that fail these are skipped, so they also decide which inputs a fix is allowed to change.
postconditionsNoPostconditions as PYTHON expressions. 'result' is the return value, e.g. 'result >= 0'. A condition that cannot be evaluated is reported as a warning, never silently skipped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that output is one line per function and that pre/postconditions are applied uniformly across all functions, which is a meaningful limitation, but it omits execution safety, possible side effects, and failure behavior.

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 three sentences, front-loads what the tool does and returns, then gives the triage use case and the important uniform-contract caveat. Every sentence contributes and there is no filler.

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

Completeness3/5

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

For a tool with five parameters and no annotations or output schema, the description covers purpose, output granularity, and a key limitation. However, it leaves unclear what 'supported function' means, what each output line contains, and how execution failures or side effects are reported.

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%, so the input schema already explains file, budget, timeout, preconditions, and postconditions in detail. The description adds only a general caveat about how pre/postconditions are applied across functions, not parameter-specific semantics.

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 states a specific verb and resource: investigate every supported function in a Python file, returning one line per function. It also gives a clear use case (triaging an unfamiliar file), though it does not name a sibling tool that performs individual investigation.

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 explicitly says to use it for triaging an unfamiliar file and warns that uniform preconditions/postconditions are blunt, advising individual investigation 'for anything that matters.' The guidance is clear but does not name an alternative tool or state hard exclusions.

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