Skip to main content
Glama

List configured Toolbox tools

list_configured_tools
Read-onlyIdempotent

List MCP and Toolbox tools configured in Studio, with read-only connection summaries that omit secret values and optional workspace filtering.

Instructions

List MCP and Toolbox tools stored in Studio. Use this for Toolbox contents. Use list_studio_catalogue for entity counts across Studio. Each tool has a connection summary (transport, auth type, OAuth mode, URL host, header and env names) that never includes a secret value. Read-only. Returns JSON with tools and tool_count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_configured_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. First observedv5.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description goes beyond them by disclosing what each record contains (transport, auth type, OAuth mode, URL host, header and env names) and guaranteeing no secret values are returned. That security guarantee is genuinely useful context not available in structured fields.

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

Conciseness4/5

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

Four short sentences, front-loaded with purpose and sibling routing before the content and return details. Nothing is obviously padded, though the closing 'Returns JSON with tools and tool_count' is partly redundant given an output schema exists.

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 annotations, a 100%-covered single-parameter schema and an existing output schema, the description covers purpose, sibling routing, and output shape adequately. The only minor gap is that it does not mention pagination or ordering behavior for the tool list.

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 single workspace parameter has 100% schema description coverage including valid identifier forms and the omit-for-active-workspace default, so the schema fully carries the load. The description adds no interpretation of the parameter, which is acceptable at baseline for a fully documented single param.

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 opens with a specific verb and resource ('List MCP and Toolbox tools stored in Studio') and immediately distinguishes itself from the sibling list_studio_catalogue, so an agent can pick between them 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing rules: 'Use this for Toolbox contents' and 'Use list_studio_catalogue for entity counts across Studio.' The when-to-use and the alternative-selection condition are both stated outright.

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