Skip to main content
Glama
Sign In

Fetch Hive

by com.fetchhive.connect
OverviewDiscussionsAdmin

Find templates

search_templates
Read-onlyIdempotent

Ready-made workflow or agent templates that fit a task, best match first: the Fetch Hive library and the account's own templates. Prefer a good template over building from scratch. Library templates are read-only; use_template gives the account its own copy to run and change.

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_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
appsNoApps the person uses, e.g. ["slack", "gmail"]. Templates using them rank higher.
kindNoDefault workflow; all searches both and every row says its kind.
limitNoHow many to return (default 5).
queryYesThe task in plain words, e.g. "weekly summary of new Stripe payments to Slack".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered; the description adds that library templates are read-only while the account has its own templates, and that use_template is the mutation path to get an editable copy. It doesn't discuss result paging or failure modes, which keeps it below a 5.

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?

Two dense sentences, front-loaded with what the tool returns and where results come from, followed by the usage rule and the read-only/copy distinction. No filler or restatement of the title.

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?

For a four-parameter read-only search with no output schema, the description covers sources, ordering, and the copy-via-use_template path, and even mentions that every row reports its kind. Slightly more on result shape or empty-result behavior would make it complete.

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% and all four parameters are documented in the schema, so the baseline is 3. The description adds only the ranking intent ('best match first'), and does not explain how apps influence ranking or how kind interacts with default behavior beyond what the schema already states.

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 names the resource (ready-made workflow or agent templates) and the two sources searched (the Fetch Hive library and the account's own templates), plus the ranking order (best match first). The verb 'search' is only implied by the name and title, so it's clear but not a fully explicit verb+resource statement.

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 states a preference rule ('Prefer a good template over building from scratch'), which tells the agent when to reach for this tool instead of constructing from scratch, and it routes the follow-up action to use_template for copying a library template into the account. That covers when-to-use and the named alternative behavior explicitly.

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

All Fetch Hive 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