Skip to main content
Glama
Sign In
HUMMBL MCP Server

HUMMBL MCP Server

by hummbl-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Problem Patterns

search_problem_patterns

Search for pre-defined problem patterns to get recommended transformations and top mental models for solving your specific problem.

Instructions

Find pre-defined problem patterns with recommended transformations and top models based on a search query.

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": {
      "query": "<query>"
    },
    "name": "search_problem_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query (minimum 2 characters)

Output Schema

NameRequiredDescriptionDefault
queryYes
patternCountYes
patternsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3
  2. Removedv1.0.0
  3. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided. The description only states it finds patterns and recommendations, without disclosing whether the operation is read-only, requires authentication, or any pagination or sorting 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?

Single clear sentence with no extraneous words. Front-loaded with the action and resource.

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?

The tool has an output schema, so return values are documented elsewhere. For a simple search with one parameter, the description sufficiently explains what is returned. Minor gaps exist but overall adequate given low complexity.

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% with adequate description of the 'query' parameter. The tool description adds context about the nature of results (pre-defined patterns, recommended transformations, top models), but does not add further semantic detail to parameters.

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 it finds pre-defined problem patterns with associated transformations and models. It distinguishes from sibling tools like 'search_models' and 'recommend_models' by focusing on patterns rather than directly on models or workflows.

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 like 'search_models' or 'find_workflow_for_problem'. The description implies use for problem pattern search, but does not specify when not to use it or provide explicit context.

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

Deploy Server

Other Tools