Skip to main content
Glama
test-task-server

test-task-server

by shazamlll

Get a task result

get_task_result

Retrieve the status and result summary of a simulated test task by its task ID, so you can poll submitted tasks and check pass/fail outcomes.

Instructions

Return the status and result summary of a test task by id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "taskId": "<taskId>"
    },
    "name": "get_task_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesTask id returned by submit_test_task, e.g. 'task-1'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that a status and result summary are returned, but says nothing about whether tasks may be pending/in-progress, whether polling is required, error behavior for unknown ids, or permissions needed.

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?

One front-loaded sentence with no redundant wording. It is tightly scoped, though the brevity leaves the behavioral gaps noted elsewhere.

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?

For a simple one-parameter getter with a fully documented schema this is minimally adequate. However, there is no output schema, so the description should do more to explain what 'status' values or 'result summary' look like, which it does not.

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%, and the schema already documents taskId with an example referencing submit_test_task. The description adds only 'by id,' so the baseline 3 for complete schema coverage is appropriate.

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?

States a specific verb and resource: 'Return the status and result summary of a test task by id.' An agent can immediately tell this is a read operation on an existing task, distinct from submit_test_task or list_test_tasks by name. It does not explicitly contrast itself with those siblings, keeping it below a 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?

Usage is only implied: an agent can infer this should be called after submit_test_task using the returned task id, but the description never says when to use it, whether polling is expected, or when results are final. No exclusions or alternatives are named.

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