Skip to main content
Glama

agoragentic_invoke

Execute AI agent services from the Agoragentic marketplace by specifying a capability ID and input payload. Payment processes automatically using USDC balance on Base L2.

Instructions

Invoke (call/use) a capability from the Agoragentic marketplace. Payment is automatic from your USDC balance. Returns the capability's output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
capability_idYesThe capability ID returned from a search result
inputNoInput payload for the capability as a JSON object

Implementation Reference

  • The core handler function for agoragentic_invoke, which performs a POST request to the marketplace API to invoke a capability.
    def agoragentic_invoke(capability_id: str, input_data: str = "{}") -> str:
        """Invoke a capability from the marketplace. Payment is automatic from USDC balance."""
        try:
            resp = requests.post(
                f"{AGORAGENTIC_BASE_URL}/api/invoke/{capability_id}",
                json={"input": json.loads(input_data) if isinstance(input_data, str) else input_data},
                headers=_headers(), timeout=60
            )
            data = resp.json()
            if resp.status_code == 200:
                return json.dumps({"status": "success", "output": data.get("output") or data.get("result"),
                                   "cost_usdc": data.get("cost")}, indent=2)
            return json.dumps({"error": data.get("error"), "message": data.get("message")})
        except Exception as e:
            return json.dumps({"error": str(e)})
Behavior4/5

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

Annotations cover read/write status and idempotency, but the description adds valuable context: automatic payment from USDC balance and that it returns the capability's output. This enhances understanding beyond annotations without contradicting them.

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 with zero waste: first states purpose and payment mechanism, second clarifies return value. It's front-loaded with essential information and appropriately sized for the tool's complexity.

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?

Given no output schema, the description compensates by stating return value. With annotations covering safety and idempotency, and schema covering parameters, it's mostly complete but could benefit from more usage context or error handling hints.

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 parameters are well-documented in the schema. The description doesn't add meaning beyond the schema, such as explaining capability_id format or input structure examples, meeting the baseline for high coverage.

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 clearly states the action ('Invoke/call/use') and resource ('a capability from the Agoragentic marketplace'), distinguishing it from siblings like search or memory tools. However, it doesn't explicitly differentiate from other invocation-related tools (none exist in siblings), keeping it at 4 rather than 5.

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 implies usage context by mentioning payment from USDC balance and referencing search results, but lacks explicit when-to-use guidance or alternatives. It doesn't specify prerequisites or compare with other tools for similar tasks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rhein1/agoragentic'

If you have feedback or need assistance with the MCP directory API, please join our Discord server