Skip to main content
Glama
InDate
by InDate

inspect

Inspect and debug code by retrieving call stacks, variables, evaluating JavaScript expressions, or searching code and function definitions.

Instructions

Inspect and debug code. Actions: getCallStack (get call stack when paused), getVariables (get variables in call frame), evaluateExpression (evaluate JavaScript), searchCode (search code by pattern), searchFunctions (find function definitions)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (for searchCode action default: 100, for searchFunctions default: 50)
actionYesInspection action: getCallStack (get call stack when paused), getVariables (get variables in call frame), evaluateExpression (evaluate JavaScript), searchCode (search code by pattern), searchFunctions (find function definitions)
filterNoRegex filter for variable names (for getVariables action) - applies to ALL scopes. Required when too many variables exist
isRegexNoTreat as regex (for searchCode action, default: true)
patternNoRegex pattern (required for searchCode action)
maxDepthNoMax expansion depth (for getVariables and evaluateExpression actions, default: 2). Auto-reduced if response too large
maxTokensNoMax tokens for getVariables response (default: 1000). Depth auto-reduced to fit, filter required if still exceeded
urlFilterNoURL filter regex (for searchCode and searchFunctions actions)
expressionNoJavaScript expression (required for evaluateExpression action)
callFrameIdNoCall frame ID (required for getVariables, optional for evaluateExpression)
functionNameNoFunction name (required for searchFunctions action)
caseSensitiveNoCase sensitive (for searchCode and searchFunctions actions, default: false)
expandObjectsNoExpand objects/arrays (for getVariables and evaluateExpression actions, default: true)
includeGlobalNoInclude global scope (for getVariables action, default: false)
connectionReasonNoConnection reference (use the reference from launchChrome output, e.g., "unnamed-connection-default" or your renamed tab)
Behavior2/5

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

No annotations provided. Description lists actions but does not disclose behavioral traits such as side effects, permission requirements, or limitations. The tool appears to be a grouping of multiple sub-functions, but this is implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is somewhat lengthy with a bullet-style list, but the structure is clear. Could be more concise by removing redundancy with 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?

With 15 parameters and no output schema, the description fails to provide a comprehensive understanding of the tool's overall behavior. It only lists actions without explaining how they relate or what the tool returns.

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 baseline is 3. The description repeats some parameter info from the schema (e.g., action enums) but does not add significant new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'Inspect and debug code' with a list of actions, which gives a general purpose. However, it lacks specificity to distinguish from sibling debugging tools like 'breakpoint' or 'console'.

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?

No guidance on when to use this tool versus alternatives. The description does not mention when not to use it or how it differs from sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/InDate/cdp-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server