Skip to main content
Glama
Sign In
start-work

start-work

by BardCreates
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get ticket context

get_ticket_context
Read-only

Retrieve a ticket’s description, acceptance criteria, discussion, parent, and child tickets as a consolidated work brief to plan and execute assigned work.

Instructions

A ticket's description, acceptance criteria and discussion, plus its parent and child tickets, as a work brief.

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": {
      "number": "<number>"
    },
    "name": "get_ticket_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's added value is the traversal behavior: it discloses that related parent and child tickets are pulled in beyond the requested ticket. It does not say how deep that hierarchy goes, whether missing parents or long discussions are truncated, or what happens for an invalid ticket number.

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?

A single tight sentence with the primary content listed first and the relational context after, which is the right ordering. Its only weakness is that the fragment lacks an explicit action verb, which slightly slows interpretation.

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?

With no output schema, the description does some work by enumerating the content sections returned. However, for a tool that fans out across a ticket hierarchy, it omits the practical details an agent needs — traversal depth, payload size or truncation, and behavior on unknown ticket numbers.

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?

There is a single required parameter with 0% schema description coverage, so the description is the only source of meaning. It establishes that 'number' refers to a ticket, but gives no format, example, or statement about what identifiers are valid, leaving the agent to guess.

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?

The description names the resource and its exact payload: description, acceptance criteria, discussion, plus parent and child tickets, framed as a 'work brief'. The verb is elided (it reads as a noun phrase), but what the tool delivers is unambiguous and distinct from siblings like list_my_tickets or set_ticket_status.

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 when-to-use guidance and no mention of the alternatives. An agent must infer that this is the read path for gathering context before acting via start_ticket or set_ticket_status, and there is no statement of when this is preferable to list_my_tickets.

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