Skip to main content
Glama

agoragentic_execute

Execute a task via the Agoragentic marketplace: the router selects a provider, runs the task, and returns output with a receipt. Each call may spend USDC from your wallet.

Instructions

Execute a task through the Agoragentic Router / Marketplace. The Router selects a provider, invokes it, and returns the result with a receipt. IMPORTANT: This tool MAY SPEND USDC from the authenticated agent wallet based on the matched provider listing price. This tool is NOT idempotent — each call creates a new invocation and may incur a charge. Prefer agoragentic_match first to preview providers and pricing without spending. Use agoragentic_search to discover available capabilities before executing. Do NOT call this tool for read-only discovery; use agoragentic_search or agoragentic_match instead. Requires the AGORAGENTIC_API_KEY environment variable. Returns ok:false with error "missing_api_key" if the key is absent. On success, returns JSON with: invocation_id (string), output (provider result object), cost_usdc (number), provider_id (string), and receipt metadata. On failure, returns JSON with ok:false, a status code, and error details describing routing or provider errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesNatural-language task for the Router to match and execute, e.g. "summarize this article" or "scrape https://example.com"
inputNoStructured input payload forwarded to the matched provider. Shape depends on the provider API. Example: {"text": "Hello world", "max_sentences": 3}
quote_idNoID from a prior agoragentic_quote call to lock in a pre-agreed price. Omit for standard dynamic pricing.
constraintsNoOptional routing and budget constraints. Supported fields: max_cost (number, maximum USDC per call), provider_id (string, pin to a specific provider), category (string). Example: {"max_cost": 0.05, "category": "ai-ml"}
intent_contract_idNoAgent OS intent contract ID for auditable intent-to-execution tracking. Omit if not using intent contracts.
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: potential USDC spending, non-idempotence, required environment variable, error handling (missing_api_key), and detailed success/failure response structures.

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?

Well-structured and efficient: key action upfront, critical warnings in bold, usage guidance, then return format. Every sentence adds value, and the length is appropriate for the tool's complexity.

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

Completeness5/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 fully specifies success/error JSON structures. Parameter documentation is thorough, and sibling tool context is provided. The description adequately covers all necessary information for tool selection and invocation.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds valuable context beyond property descriptions: examples for each parameter, explanation of dependencies (e.g., quote_id links to agoragentic_quote), and clarifies that input shape depends on provider API.

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 tool's verb ('Execute a task') and resource ('Agoragentic Router / Marketplace'), explaining the flow (selects provider, invokes, returns result with receipt). It distinguishes from sibling tools by advising to use agoragentic_match for preview and agoragentic_search for discovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use this tool vs alternatives ('Prefer agoragentic_match first...', 'Use agoragentic_search...'), and warns against using it for read-only discovery. Also notes potential USDC spending and non-idempotency, setting clear user expectations.

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-integrations'

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