AgentPMT - Marketplace For Autonomous Agents

AgentPMT Workflow Skills

AgentPMT-Workflow-Skills

AgentPMT Workflow Skills - Fetch, Search, and Use Agent Workflows and Skills. Use to retrieve, initiate, and complete workflows.

Input Schema

TableJSON Schema

Name	Required	Description
`skip`	No	Number of results to skip for pagination
`limit`	No	Maximum results to return (1-200)
`query`	No	Optional substring search over name/description (case-insensitive)
`action`	Yes	Operation to perform: search, browse_industry, get_workflow_skill, start_workflow, end_workflow, get_active_workflow, get_instructions
`rating`	No	Workflow rating from 1-5 stars (required for end_workflow)
`comment`	No	Comment about the workflow experience (required for end_workflow)
`include`	No	Comma-separated entity types to include for browse_industry: workflows, content, categories. Defaults to all.
`industry`	No	Industry name or slug (required for browse_industry). Returns linked workflows, content, and categories.
`skill_id`	No	Skill chain ObjectId or slug (required for get_workflow_skill, start_workflow, end_workflow)
`publisher`	No	Filter by publisher username (case-insensitive substring match)
`categories`	No	Comma-separated category names to filter by
`industry_tags`	No	Comma-separated industry tag names to filter by
`suggested_improvements`	No	Suggested improvements or changes to the workflow (optional)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 13, 2026
- addedInput schema / $schema
```
Added value: +"https://json-schema.org/draft/2020-12/schema"
```

Changed1 schema field changedMar 13, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "search",
-  "browse_industry",
-  "get_workflow_skill",
-  "start_workflow",
-  "end_workflow",
-  "get_active_workflow",
-  "get_instructions"
-]New value: +[
+  "browse_industry",
+  "end_workflow",
+  "get_active_workflow",
+  "get_instructions",
+  "get_workflow_skill",
+  "search",
+  "start_workflow"
+]

Changed4 schema fields changedMar 9, 2026

changedInput schema / properties / action / description

Previous value: -"Operation to perform: search, get_workflow_skill, start_workflow, end_workflow, get_active_workflow, get_instructions"New value: +"Operation to perform: search, browse_industry, get_workflow_skill, start_workflow, end_workflow, get_active_workflow, get_instructions"

changedInput schema / properties / action / enum

Previous value: -[
-  "search",
-  "get_workflow_skill",
-  "start_workflow",
-  "end_workflow",
-  "get_active_workflow",
-  "get_instructions"
-]New value: +[
+  "search",
+  "browse_industry",
+  "get_workflow_skill",
+  "start_workflow",
+  "end_workflow",
+  "get_active_workflow",
+  "get_instructions"
+]

addedInput schema / properties / include

Added value: +{
+  "description": "Comma-separated entity types to include for browse_industry: workflows, content, categories. Defaults to all.",
+  "type": "string"
+}

addedInput schema / properties / industry

Added value: +{
+  "description": "Industry name or slug (required for browse_industry). Returns linked workflows, content, and categories.",
+  "type": "string"
+}

Changed9 schema fields changedFeb 19, 2026

addedInput schema / properties / categories

Added value: +{
+  "description": "Comma-separated category names to filter by",
+  "type": "string"
+}

addedInput schema / properties / industry_tags

Added value: +{
+  "description": "Comma-separated industry tag names to filter by",
+  "type": "string"
+}

addedInput schema / properties / limit / maximum
```
Added value: +200
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

addedInput schema / properties / publisher

Added value: +{
+  "description": "Filter by publisher username (case-insensitive substring match)",
+  "type": "string"
+}

addedInput schema / properties / rating / maximum
```
Added value: +5
```
addedInput schema / properties / rating / minimum
```
Added value: +1
```

changedInput schema / properties / skill_id / description

Previous value: -"Skill chain ObjectId (required for get_workflow_skill, start_workflow, end_workflow)"New value: +"Skill chain ObjectId or slug (required for get_workflow_skill, start_workflow, end_workflow)"

addedInput schema / properties / skip / minimum
```
Added value: +0
```

First observedFeb 18, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. It mentions 'initiate and complete workflows' implying state changes, but provides no details about permissions, side effects, or whether operations are reversible. This is insufficient for a mutation-heavy tool.

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

Conciseness3/5

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

The description is a single short sentence with no wasted words. However, it is arguably too concise—key information is omitted. Conciseness is achieved at the expense of completeness, resulting in a mediocre score.

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?

Given the tool's complexity (13 parameters, no output schema) and the presence of sibling tools, the description is too sparse. It does not explain return values, pagination behavior, or how actions interact. An agent would lack critical context to use this tool effectively.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; it does not explain parameter relationships, required combinations, or usage patterns. The schema itself is clear, so the description does not harm but offers no extra value.

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 states the general purpose: fetching, searching, and using workflows/skills. However, it is vague and does not distinguish this tool from siblings like AgentPMT-Workflow-Creator or AgentPMT-Tool-Search-and-Execution. No specific resource or scope is given.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites or typical contexts. The agent receives no decision support.

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

All AgentPMT - Marketplace For Autonomous Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?