Skip to main content
Glama
Sign In
start-work

start-work

by BardCreates
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List my tickets

list_my_tickets
Read-only

Retrieve open tickets assigned to you, highest priority first, to choose what to work on next. Filter by status if needed.

Instructions

Open tickets assigned to me, highest priority first. Use this to pick what to work on next.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_tickets"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOnly tickets in this status (default: all open).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description's job is lighter. It usefully adds the default scope (open tickets) and the priority ordering, but says nothing about result size, pagination, or what fields come back, which matters for a list tool.

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 short sentences with zero filler, and the scope plus ordering are front-loaded before the usage hint. Every clause 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?

For a one-optional-parameter read tool with no output schema, the description covers scope, default filtering, ordering, and intent. The only real gap is return-shape or volume expectations, which is minor given the tool's simplicity.

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 100% and the single status parameter is fully documented with an enum and a default note, so the schema carries the load. The description's "open tickets" phrasing is consistent with the schema default but adds no new syntax or filtering detail beyond it.

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 resource (tickets), scope (assigned to me, open), and ordering (highest priority first), which is far more than restating the name. It does not explicitly contrast with siblings like get_ticket_context or set_ticket_status, but those are clearly different operations, so the distinction is implicit rather than stated.

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

Usage Guidelines4/5

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

"Use this to pick what to work on next" gives a concrete usage context that tells the agent when this tool is the right choice. It stops short of naming alternatives or exclusions (e.g., when to use get_ticket_context instead), so it is clear context without full routing guidance.

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