Skip to main content
Glama
S3bRR

AgentTasker MCP Server

by S3bRR

execute

Execute a single task—such as running Python code, sending an HTTP request, or executing a shell command—and return its structured result.

Instructions

Run one task and return its result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoTask name
task_typeYesTask type
codeNoPython code
timeoutNoTimeout seconds
urlNoTarget URL
methodNoHTTP method
headersNoHeaders
bodyNoRequest body
verify_sslNoVerify SSL
max_body_bytesNoMax response bytes
retriesNoRetry count
retry_backoff_secondsNoRetry backoff seconds
queryNoSearch query
providersNoDiscovery providers
max_resultsNoMax results
fetch_top_resultsNoFetch top result pages
fetch_max_charsNoChars per fetched page
max_linksNoMax links
max_text_charsNoMax extracted chars
include_htmlNoInclude raw HTML
extract_linksNoInclude links
extract_headingsNoInclude headings
link_include_patternNoRegex for kept links
commandNoCommand
pathNoFile path
contentNoFile content
modeNow or a
output_modeNofull or compactcompact
Behavior2/5

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

No annotations exist, and the description adds no behavioral context beyond the basic action. It does not disclose security requirements, side effects, rate limits, or error handling, leaving a significant gap for a tool with 28 parameters.

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 extremely concise (6 words) and front-loaded with the core purpose. However, for a tool with 28 parameters, slightly more detail could aid understanding without losing conciseness.

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?

Given the high parameter count and no output schema, the description is insufficiently complete. It lacks information about return values, error scenarios, and how to properly configure the many task types.

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 baseline is 3. The description does not add any meaning beyond the schema's parameter descriptions, which are already present.

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 'Run one task and return its result' clearly states the action (run) and the resource (task), and implicitly distinguishes from sibling 'execute_batch' by specifying a single task.

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?

No guidance is provided on when to use this tool versus execute_batch, or on prerequisites, context, or exclusions. The agent must infer usage from the name alone.

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/S3bRR/agent-tasker-mcp'

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