Skip to main content
Glama
soil-dev

capsulemcp

by soil-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_task

Read-only

Fetch a task by its numeric ID to view its description, due date, owner, completion state, and linked record (party, opportunity, or project).

Instructions

Fetch a single task by its numeric id. Returns the task's description, due date, owner, completion state, and the entity it's attached to (party / opportunity / project, if any — standalone tasks not tied to a record are also valid). For batch fetches of up to 50 tasks at once, use get_tasks instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask ID
embedNoComma-separated embeds. Valid tokens: party, opportunity, project, owner, nextTask.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.0
    • addedInput schema / required
      Added value: +[
+  "id"
+]
  2. Changed1 schema field changedv2.2.0
    • addedInput schema / properties / embed
      Added value: +{
+  "description": "Comma-separated embeds. Valid tokens: party, opportunity, project, owner, nextTask.",
+  "type": "string"
+}
  3. Addedv1.7.0
  4. Removedv1.6.2
  5. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds useful behavioral context: it returns specific fields, may return tasks not attached to any entity, and treats standalone tasks as valid. This goes beyond the structured annotations.

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 with no filler. The primary purpose and return contents come first, and the batch alternative is presented in one clear follow-up sentence.

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?

With no output schema, the description compensates by listing the key returned fields and clarifying the attached-entity behavior. It could have said more about the optional embed parameter's effect on the response, but that is already covered in the schema, so the definition is sufficiently complete for a simple read tool.

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%, with id and embed fully described in the schema. The description itself adds little parameter-level meaning beyond confirming the id is numeric, so baseline 3 is appropriate.

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 the tool fetches a single task by numeric id, listing the returned fields. It explicitly distinguishes itself from get_tasks by noting batch fetching is the sibling's job, so an agent can select it unambiguously.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use get_tasks instead for batch fetches of up to 50 tasks. This gives a direct when-to-use versus when-not-to-use directive, which is exactly what an agent needs.

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