AgentPMT - Marketplace For Autonomous Agents

AgentPMT Tool Search and Execution

AgentPMT-Tool-Search-and-Execution

AgentPMT Tool Search and Execution - Unified interface for discovering, searching, and using AgentPMT tools without MCP refresh. Access tools required for workflows and skills here.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number for pagination (1-based). Used when listing tools.
`query`	No	Search query for text and semantic matching. If provided, performs hybrid search.
`action`	Yes	Operation to perform: get_tools (discover tools - list/search/workflow), get_schema (full tool schema by ID), request_credentials (email user to add credentials), call_tool (execute a tool), get_instructions (help)
`message`	No	Custom message to include in credential request notification (for request_credentials action)
`tool_id`	No	Tool/product ID (required for get_schema and use actions)
`page_size`	No	Number of results per page (1-100)
`tool_name`	No	Alternative: Tool name to search for (for use action, searches then executes first match)
`parameters`	No	Parameters to pass to the tool when using 'use' action
`workflow_id`	No	Workflow/skill chain ID. If provided, returns all tools from that workflow.

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: -[
-  "get_tools",
-  "get_schema",
-  "request_credentials",
-  "call_tool",
-  "get_instructions"
-]New value: +[
+  "call_tool",
+  "get_instructions",
+  "get_schema",
+  "get_tools",
+  "request_credentials"
+]

First observedFeb 18, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It mentions the tool performs multiple actions (discover, search, use) but does not disclose side effects, error handling, or specifics like tool execution behavior.

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?

The description is concise with two sentences. It front-loads the core idea but repeats the title. It is efficient but could be slightly more structured.

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?

Despite the schema providing parameter details, the description lacks context on return values, error handling, and how to effectively use the different actions. For a tool with 9 parameters and multiple actions, the high-level summary is insufficient.

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%, so baseline is 3. The description does not add additional meaning beyond the schema; it only reiterates the action enum conceptually without explaining parameter relationships.

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 states the tool is a 'unified interface for discovering, searching, and using AgentPMT tools' and mentions avoiding MCP refresh. This clearly indicates the tool's purpose and differentiates it from sibling tools like reporting issues or creating workflows.

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?

The description gives context by saying 'without MCP refresh' and 'Access tools required for workflows and skills here', implying when to use it. However, it does not explicitly state when not to use it or provide direct comparisons to alternatives.

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?