Skip to main content
Glama

aw.catalog

Read-only

Find supported public beta workflows by task.

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": "aw.catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes the filtering constraint that only supported public-beta entries are returned, which is useful scoping context, but says nothing about pagination behavior, match semantics, or result ordering for a search endpoint.

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?

A single short sentence with no filler, and the resource and lookup axis are front-loaded. It is efficient but borders on under-specified rather than maximally concise — one more sentence on paging or query semantics would have cost little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter search tool with no output schema, the description should at minimum explain what a result looks like and how the query/limit/offset triple behaves. Neither is present, leaving the agent to guess at pagination and matching behavior before calling.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must carry the burden and does not. "By task" weakly implies that query accepts a task description, but limit and offset are left entirely unexplained, and there is no hint about query matching semantics, result caps, or how to page through the catalog.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a verb ("Find") and a resource ("supported public beta workflows"), plus a lookup axis ("by task"), so the general purpose is inferable. However, "workflows" is never grounded — it's unclear whether these are automation recipes, job templates, or API operations — and the "public beta" qualifier adds ambiguity rather than precision for an agent unfamiliar with the catalog's contents.

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 when-to-use guidance is given: nothing says whether this should be called before invoking a workflow, how it relates to sibling tools like aw.jobs.list or aw.transfer.guide, or what to do when the catalog returns nothing. The only implied usage is that a task description can be searched, which is not actionable guidance.

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