googleapis/mcp-toolbox · error
description is required for tool %q
Error message
description is required for tool %q
What it means
Configuration-time validation in Initialize: the looker-get-connection-databases tool entry in tools.yaml omits its description, which Toolbox requires for the tool manifest.
Source
Thrown at internal/tools/looker/lookergetconnectiondatabases/lookergetconnectiondatabases.go:71
}
type Config struct {
tools.ConfigBase `yaml:",inline"`
Type string `yaml:"type" validate:"required"`
Source string `yaml:"source" validate:"required"`
Annotations *tools.ToolAnnotations `yaml:"annotations,omitempty"`
}
// validate interface
var _ tools.ToolConfig = Config{}
func (cfg Config) ToolConfigType() string {
return resourceType
}
func (cfg Config) Initialize(context.Context) (tools.Tool, error) {
if cfg.Description == "" {
return nil, fmt.Errorf("description is required for tool %q", cfg.Name)
}
connParameter := parameters.NewStringParameter("conn", "The connection containing the databases.")
params := parameters.Parameters{connParameter}
// finish tool setup
return Tool{
BaseTool: tools.NewBaseTool(
cfg,
tools.GetAnnotationsOrDefault(cfg.Annotations, tools.NewReadOnlyAnnotations),
tools.Manifest{Description: cfg.Description, Parameters: params.Manifest(), AuthRequired: cfg.AuthRequired},
params,
),
}, nil
}
// validate interface
var _ tools.Tool = Tool{}View on GitHub (pinned to 8cc6e09de2)
Solutions
- Add a non-empty description to the tool entry in tools.yaml
- Check YAML indentation so description parses as a string rather than null
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at internal/tools/looker/lookergetconnectiondatabases/lookergetconnectiondatabases.go:71 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of googleapis/mcp-toolbox@8cc6e09de2 (2026-09-05).
Data as JSON: /api/errors/4a5dfd00af80bb74.
Report an issue: GitHub.