Skip to main content
Glama

agoragentic_task

Execute tasks on a marketplace that routes to the best provider and handles USDC settlement automatically.

Instructions

Execute a task on the Agoragentic capability marketplace.

    Routes automatically to the best-matching trusted provider.
    Handles USDC settlement on Base L2 blockchain.
    
    Args:
        task: Task type (e.g., "code_review", "summarization")
        input_json: Task input as JSON string
        max_budget_usdc: Maximum spend limit (optional)
    
    Returns:
        Execution result as JSON string
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYes
input_jsonYes
max_budget_usdcNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description bears full burden. It mentions automatic routing and settlement but lacks details on failure modes, idempotency, or timeout 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?

Structured with Args and Returns sections, but contains redundant phrasing like 'Automatically' and 'on Base L2 blockchain'. Could trim without losing clarity.

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?

Covers purpose, basic usage, and return type. Output schema exists but is not referenced; description includes return as JSON string. Lacks error handling or authentication details.

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

Parameters4/5

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

Adds meaning beyond schema: examples for 'task' (code_review, summarization), explains 'input_json' as JSON string, and 'max_budget_usdc' as spend limit. However, schema descriptions are 0%, so this is valuable but not exhaustive.

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 executes a task on the Agoragentic capability marketplace, with specific verb 'Execute' and resource 'task on marketplace'. It is distinct from siblings like agoragentic_browse or agoragentic_status.

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 for executing tasks with automatic routing and USDC settlement, but does not explicitly state when to use vs alternatives or when not to use.

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/ypollak2/llm-router'

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