Sergio by Serviche

Create a task

create_task

Idempotent

Adds a task to the team's work queue, optionally tied to a client or conversation and due at a time (ISO 8601). Pass the same idempotency_key when retrying; a repeat returns the original task.

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": {
      "title": "<title>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_task"
  }
}

Input Schema

Name	Required	Description
`title`	Yes
`due_date`	No
`priority`	No
`client_id`	No
`description`	No
`conversation_id`	No
`idempotency_key`	Yes	Your id for this operation (8-128 of A-Z a-z 0-9 . _ : -). Reuse it on every retry of the same operation; use a new one for a new operation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description earns credit by making that concrete: a repeat with the same key returns the original task rather than duplicating. It also discloses that tasks land in a shared team queue rather than a private list, which the annotations do not convey. It stops short of stating permission requirements or what the first successful call returns.

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 sentences, front-loaded with the core action, then the retry contract. No filler, and every clause carries information an agent needs before calling.

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 7-parameter mutation with no output schema, the description covers the essential creation and idempotency semantics but leaves the priority enum and body/description fields unexplained, and only obliquely hints at the return value via the retry case. Adequate, not complete.

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 only 14% (just idempotency_key), so the description must carry weight for the other six parameters. It clarifies due_date as ISO 8601 and explains that client_id/conversation_id are optional ties, but never mentions priority (the only enum) or the description field, leaving real gaps.

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 ('Adds a task to the team's work queue') plus scope details: optional client/conversation linkage and a due time. It does not explicitly contrast with sibling mutators like update_task, assign_task, or snooze_task, but 'Adds' makes the create semantics unambiguous.

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 implied by the creation framing and the retry guidance ('Pass the same idempotency_key when retrying'), which is genuinely useful. There is no explicit when-not guidance or routing to alternatives such as update_task or assign_task for existing tasks.

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

All Sergio by Serviche tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?