Skip to main content
Glama

ProofTask public

findTemplates

Read-onlyIdempotent

[No connection needed] Search public delivery templates (scope, completion criteria, required evidence) by scenario, for example "n8n workflow" or "chatbot". Read-only; creates nothing.

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": "findTemplates"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords describing the delivery.
industryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real value beyond that with "[No connection needed]" (no auth/setup required) and scopes over open-world public data, though "creates nothing" largely restates destructiveHint=false.

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 compact sentences, front-loaded with the key constraint and purpose. Every clause carries information: capability, content shape, examples, connection requirement, and safety.

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 two-optional-parameter search tool with no output schema, the description covers what is searched, what a result contains, and that no setup is needed. Minor gaps only: nothing about result volume/ordering or how the industry filter interacts with the query.

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 50%: query is documented, industry is not. The description compensates partially by giving example query strings that show the expected granularity and vocabulary, but says nothing about the industry filter or whether parameters are combinable, leaving the undocumented half uncovered.

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?

Uses a specific verb+resource ("Search public delivery templates") and clarifies what a template contains (scope, completion criteria, required evidence). The plural "templates" plus search framing implicitly distinguishes it from the singular getTemplate sibling, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

Provides concrete example queries ("n8n workflow", "chatbot") that imply when the tool is appropriate, and the "[No connection needed]" note signals it can be used before setup. However, there is no explicit guidance on when to use this versus getTemplate, which likely fetches a single template by id.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources