Skip to main content
Glama
Sign In
Recruit CRM MCP

Recruit CRM MCP

by ebragas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_task

Retrieve full details of a specific task by its ID, with the description normalized from HTML to Markdown.

Instructions

Get full details for a specific task by ID.

The description field is normalized from the CRM's stored HTML to Markdown before being returned to the model.

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_id": "<task_id>"
    },
    "name": "get_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.19.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must disclose all behavioral traits. It adds that the 'description' field is normalized from HTML to Markdown, which is valuable. However, it does not mention error handling, authentication, or rate limits, leaving gaps.

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?

Two concise sentences, front-loaded with the purpose. The second sentence adds a critical behavioral detail without waste. Every word earns its place.

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

Completeness4/5

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

Given the presence of an output schema, the description need not detail return values. It covers input (task_id) and a key behavioral trait (description normalization). For a simple get tool, this is nearly complete, though error handling or default responses are missing.

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 coverage is 0% (no parameter descriptions in schema). Baseline is 4 for zero schema parameters, but the description only adds 'by ID' which does not significantly enhance understanding beyond the schema's 'task_id' property name. Minimal compensation.

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 'Get full details for a specific task by ID'. It specifies the verb (get), resource (task), and identifier (ID), distinguishing it from sibling tools like search_tasks which list or search tasks.

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?

The description provides no explicit guidance on when to use this tool vs alternatives such as search_tasks. It only implies usage when a task ID is known, but does not state exclusions or preferred contexts.

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