Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

list_tool_packages

Discover available tool packages and identify the currently loaded one in the ServiceNow MCP Server to manage integration capabilities.

Instructions

Lists available tool packages and the currently loaded one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
random_stringYesDummy parameter for no-parameter tools

Implementation Reference

  • Core implementation function that computes and returns the dictionary with current tool package and list of available packages.
    def _list_tool_packages_impl(self) -> Dict[str, Any]:
        """Implementation logic for the list_tool_packages tool."""
        available_packages = list(self.package_definitions.keys())
        return {
            "current_package": self.current_package_name,
            "available_packages": available_packages,
            "message": (
                f"Currently loaded package: '{self.current_package_name}'. "
                f"Set MCP_TOOL_PACKAGE env var to one of {available_packages} to switch."
            ),
        }
  • Dispatch logic in call_tool_impl that handles the list_tool_packages tool invocation, checks package, calls impl, serializes to JSON, and returns TextContent.
    if name == "list_tool_packages":
        if self.current_package_name == "none":
            raise ValueError(
                "Tool 'list_tool_packages' is not available in the 'none' package."
            )
        result_dict = self._list_tool_packages_impl()
        serialized_string = json.dumps(result_dict, indent=2)
        # Return a list with a TextContent object
        return [types.TextContent(type="text", text=serialized_string)]
  • Registers the list_tool_packages tool in the list_tools MCP endpoint response (conditionally if not 'none' package), including name, description, and input schema.
    types.Tool(
        name="list_tool_packages",
        description="Lists available tool packages and the currently loaded one.",
        inputSchema={
            "type": "object",
            "properties": {
                "random_string": {
                    "type": "string",
                    "description": "Dummy parameter for no-parameter tools",
                }
            },
            "required": ["random_string"],
        },
    )
  • Input schema for list_tool_packages tool, using a dummy required string parameter since MCP requires at least one.
    inputSchema={
        "type": "object",
        "properties": {
            "random_string": {
                "type": "string",
                "description": "Dummy parameter for no-parameter tools",
            }
        },
        "required": ["random_string"],
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool lists packages but doesn't add context like whether it's a read-only operation, if it requires authentication, how results are formatted, or any rate limits. For a tool with no annotations, this leaves significant behavioral gaps.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly. Every part of the sentence earns its place by conveying essential information.

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?

Given the tool's low complexity (a list operation with one dummy parameter) and no output schema, the description is minimally adequate but incomplete. It lacks details on behavioral traits (e.g., read-only nature, result format) that would be helpful for an agent, especially with no annotations. It meets basic needs but leaves room for improvement in context.

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?

The input schema has 100% description coverage, with the parameter 'random_string' documented as a dummy for no-parameter tools. The description doesn't add any meaning beyond this, as it doesn't mention parameters at all. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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 clearly states the tool's purpose with a specific verb ('Lists') and resource ('available tool packages and the currently loaded one'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'list_workflows' or 'list_script_includes', which also list resources, so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention context, prerequisites, or exclusions, leaving the agent to infer usage based on the name alone. This lack of explicit guidelines reduces its effectiveness in tool selection.

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/vparlapalli490/MCP'

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