Skip to main content
Glama

AI Fusion One

ALL AI Forms workflow catalog

allaiforms_workflows
Read-onlyIdempotent

Free. Step-by-step legal/admin workflows sold by sister brand ALL AI Forms (All AI LLC): name, page URL, price, Stripe pay link, step and linked-form counts. Cached ~15 min from allaiforms.com/catalog.json, sanitized and host-allowlisted. Purchases happen on ALL AI Forms, not through this server. Not legal advice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Goes well beyond the annotations: discloses the free/cached ~15 min data source (allaiforms.com/catalog.json), sanitization and host-allowlisting, and that purchases are handled externally. The only gap is no note on result size or empty-catalog behavior. Nothing contradicts readOnlyHint/idempotentHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with purpose, then source/caching, then the purchase-location caveat. Slightly list-like and packed, but every clause (price, Stripe link, step counts, caching, non-advice) carries information.

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 zero-parameter read-only catalog tool with no output schema, the definition covers source, freshness, safety handling, purchasing boundary, and field contents. It lacks only explicit return-shape/volume details, which is a minor omission here.

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

Parameters4/5

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

Zero parameters, so the baseline is 4; the schema has no inputs to explain. The description redirects effort to explaining the returned fields and pricing/Stripe semantics instead, which is the right use of space.

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?

States a specific verb+resource: lists a catalog of paid legal/admin workflows with the fields returned (name, page URL, price, Stripe pay link, step and linked-form counts). It is clearly distinguishable from data-lookup siblings, though it doesn't name a specific alternative tool.

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?

Usage is implied by the description: it's a read-only catalog lookup for ALL AI Forms workflows, and it explicitly notes purchases happen off-server. There is no explicit when-to-use/when-not-to-use guidance or named alternative for related pricing/brand lookups (get_pricing, allai_brands).

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