Skip to main content
Glama
Sign In

Gydmation

by io.github.hacrootechnologies
OverviewDiscussionsAdmin

Search workflow templates

search_templates
Read-only
Meaning-based search over Gydmation's 1,950+ verified workflow templates.
Check here before generating from scratch.

Args:
    prompt: What you want to automate.
    app: Only templates using these apps, comma-separated, e.g. "Gmail, Slack".
    trigger: Only templates started by: webhook, schedule, manual, form,
        chat, email, app_event, sub_workflow or error.
    complexity: beginner, intermediate or advanced.
    industry: e.g. "E-commerce", "Marketing", "Support".
    limit: Maximum matches (1-25).
Each match has a template_id to pass to get_template or deploy_template.

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": {
      "prompt": "<prompt>"
    },
    "name": "search_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNo
limitNo
promptYes
triggerNo
industryNo
complexityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so safety is covered; the description adds the meaning-based (semantic, not keyword) matching semantics and the downstream chaining fact that each match carries a template_id for get_template or deploy_template. That chaining detail is genuinely useful workflow context not present in any structured field.

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?

One framing sentence plus a compact Args block and a single closing line about template_id. Front-loaded, no filler, and the structured list makes scanning trivial.

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 no output schema, the description still tells the agent what a result contains (template_id) and how to use it, and the trigger/complexity vocabularies remove the main correctness risk. Minor gap: no mention of default ordering or relevance behavior beyond 'meaning-based', but nothing essential to a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it delivers: it enumerates valid trigger values, complexity levels, the comma-separated format for app with an example, and the 1-25 bound on limit. Every parameter is made usable from prose alone.

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?

States a specific verb and resource ('meaning-based search over Gydmation's 1,950+ verified workflow templates') and disambiguates from the node-search sibling by naming templates explicitly. The corpus size and 'verified' qualifier tell an agent exactly what kind of results to expect.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

'Check here before generating from scratch' clearly positions this as the preferred first step and implicitly routes to generate_workflow, giving real when-to-use guidance rather than none. It stops short of explicit exclusions or naming the alternative tool directly, which keeps it out of the top score.

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

All Gydmation toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources