Skip to main content
Glama
Sign In
testit-mcp-server

testit-mcp-server

by iampopovich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_work_item

Read-only

Retrieve a TestIT work item by its UUID to view details, status, and metadata. Use it when you need to look up a specific work item for test management.

Instructions

Get a work item by ID (UUID).

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_work_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWork item UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds nothing beyond that. It does not say what happens when the UUID does not exist or is malformed (error vs. empty result), nor anything about the shape of the returned record.

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 short sentence with the resource and key front-loaded and no filler. The only mild redundancy is repeating the UUID hint already present in the schema.

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 single-parameter read tool with annotations and no output schema, this is close to adequate, but it leaves out error behavior for unknown IDs and any indication of what the work item payload contains. A brief clause on those points would make it 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?

The schema has 100% description coverage and already labels the single parameter as "Work item UUID." The description restates the same UUID format hint without adding syntax, sourcing, or validation detail, so it sits at the baseline for a fully documented single-parameter schema.

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 ("Get a work item") plus the lookup key ("by ID (UUID)"), so the retrieval intent is unambiguous. It does not differentiate from sibling retrievers such as get_work_item_history or get_work_item_versions, so it stops short of a 5.

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 use this versus alternatives like list_work_items or search_work_items, and no stated prerequisites for obtaining a valid work item UUID. The agent must infer that this is the direct-fetch path for a known identifier.

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