Skip to main content
Glama

get_task_parameters

Retrieve reviewed input parameters, required fields, and available live documentation for a specified task type before configuring a CapSolver task.

Instructions

Read reviewed input parameters, required fields and live documentation when available.

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": {
      "task_type": "<task_type>"
    },
    "name": "get_task_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it only hints that documentation is 'when available' — implying a variable or partial response. It does not state whether the call is read-only (implied but not asserted), what happens for an unknown task_type, or whether results are cached or live. The output schema covers return shape, but failure and availability behavior remain undisclosed.

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 filler, and the conditional 'when available' caveat is placed where it matters. It is efficient, though the brevity contributes to the semantic gaps rather than resolving them.

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?

The presence of an output schema means return values need not be described, which lightens the load. However, for a tool whose only input is an unexplained required string and whose closest siblings (get_task_schema, get_docs) are undisambiguated, the description leaves the agent without enough to choose or invoke it confidently.

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

Parameters2/5

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

The single parameter task_type has 0% schema description coverage, so the description must compensate and does not. It never explains what a task_type is, its format, or that valid values are likely obtainable via list_task_types or get_supported_tasks, leaving the required parameter effectively undefined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Read' and the resources 'input parameters, required fields and live documentation' give a rough sense of what comes back, but the phrasing is ambiguous: it is unclear whether the tool returns parameter definitions, a validated parameter set, or documentation text. It also does nothing to distinguish itself from siblings like get_task_schema or get_docs, which on names alone appear to overlap heavily.

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?

There is no guidance on when to call this instead of get_task_schema, get_supported_tasks, or get_docs, and no prerequisite such as where a valid task_type comes from. The agent is left to infer routing from tool names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.