Skip to main content
Glama
Sign In
coinopai-mcp

coinopai-mcp

by forgemeshlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_agent_automation

Fetch the full agent automation prompt and workflow steps for any automation slug. Unlock detailed instructions for a $0.01 USDC payment.

Instructions

Get the full agent automation prompt and workflow steps by slug. Costs $0.01 USDC.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_agent_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesAutomation slug (e.g. 'slack-to-notion')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.6

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only mentions a cost of $0.01 USDC, which is a behavioral trait, but does not disclose any other side effects, permissions, or limitations.

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 sentences, no redundant information. The action and resource are front-loaded. Every word contributes value.

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

Completeness3/5

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

For a simple getter with one parameter and no output schema, the description is basic but adequate. It conveys what is returned and the cost. However, it could mention that the slug must be known or that this is for exact retrieval, especially given sibling search tools.

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% as the only parameter 'slug' is described with an example. The description adds no additional meaning beyond the schema, so baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb 'Get' and the specific resource 'full agent automation prompt and workflow steps by slug'. It distinguishes from sibling tools like search_agent_automations and list_automation_categories.

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?

The description lacks guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or context are provided. The only extra info is the cost, which does not help with usage decisions.

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

Deploy Server

Other Tools