Skip to main content
Glama
Sign In
Aspro Cloud MCP

Aspro Cloud MCP

by kazan-project-manufactory
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_task

Retrieve a specific task from Aspro Cloud CRM by its unique ID to access full task details for review or further actions.

Instructions

Get a 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": {
      "id": "<id>"
    },
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description itself must convey behavioral context. 'Get a task by ID' clearly implies a read-only retrieval action and does not contradict any structured data, but it does not disclose what happens if the task is not found, error behavior, or return format specifics. It is a minimal disclosure that is not misleading but lacks deeper context.

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 a single, concise sentence with no redundant words. It front-loads the key action and resource, earning every character of its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema, no nested objects), the description adequately covers the essential usage. It clearly states what the tool does and what input it takes; the return value (the task) is self-evident from the action 'Get a task'.

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?

The input schema fully documents the single parameter 'id' with type and description 'Task ID', and the schema coverage is 100%. The description merely repeats 'by ID' without adding any new information about the parameter's semantics, such as format, constraints, or behavior when invalid.

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 'Get a task by ID' uses a specific verb and resource, clearly indicating a read operation for a single task by its ID. This distinguishes it from sibling tools like list_tasks (listing), create_task, update_task, and delete_task.

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 when a task ID is known and a single task is needed, but it provides no explicit guidance on when to use it instead of alternatives like list_tasks or get_lead. No exclusions or alternative tool references are given, so the guidance is only implied.

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