Skip to main content
Glama
Sign In
agent-pool-mcp

agent-pool-mcp

by rnd-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_scheduled_results

Retrieve results from scheduled task executions, displaying the last 20 results in newest-first order. Filter by schedule ID or project directory.

Instructions

Get results from scheduled task executions. Returns the last 20 results, newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_scheduled_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoProject directory. Defaults to current working directory.
jsonNoReturn pure JSON string instead of Markdown format.
schedule_idNoFilter results by schedule ID. Omit to get all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.3

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns the last 20 newest results, but it does not mention whether the operation is read-only, any authentication needs, rate limits, or side effects. This is insufficient for safe and reliable invocation.

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?

The description is two sentences with no wasted words. The purpose is front-loaded, and the key behavioral detail (last 20, newest first) is included efficiently.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is minimal. It covers the basic purpose and a key constraint (limit 20), but lacks information about pagination, error handling, or the relationship to other scheduling tools. It is adequate but not comprehensive.

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 the schema already documents all parameters. The description does not add any additional meaning beyond what the schema provides (e.g., clarifying the format of schedule_id or the effect of cwd). Baseline 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 resource 'results from scheduled task executions', with specific detail about returning the last 20 results newest first. This distinguishes it from sibling tools like schedule_task or cancel_schedule, which deal with scheduling rather than retrieving results.

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 viewing recent scheduled results via the mention of 'last 20 results, newest first', but it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like get_task_result. This leaves the agent to infer appropriate usage context.

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