Skip to main content
Glama

Read what Quick did

get_quick_work
Read-only

What Quick did on its own on the user's jobs: each find it worked on, newest first — the weekly find it prepares at no cost to the user (origin gift), and, when Quick works from the plan's limits (origin engine), the analysis, resume suggestions, a tailored resume copy, a cover letter or an archive of a job the profile rules out. Every step carries its result and the reason as a code. Also says whether Quick is working on its own (enabled) and whether the plan allows it (included: Sprint and Career). No quota. Args: {limit, before}.

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": "get_quick_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNo

Output Schema

NameRequiredDescriptionDefault
itemsYesWhat Quick did on each find, newest first.
enabledYesQuick is working on its own from the plan's limits.
includedYesThe plan lets Quick work on its own (Sprint and Career).
next_beforeNoPass as before for the next page; null at the end.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), yet the description adds genuinely new behavior: 'No quota', newest-first ordering, pagination via 'before', and two operational state flags — whether Quick is 'enabled' (working autonomously) and whether the plan 'included' it (Sprint and Career only). That is real information an agent cannot get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core purpose, which is good, but it is a single dense run-on sentence stuffed with proprietary vocabulary ('origin gift', 'origin engine', 'the weekly find it prepares at no cost') that costs parsing effort. The trailing 'Args: {limit, before}' is a weak structural add-on rather than an integrated explanation.

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?

An output schema exists, so the description needn't enumerate return fields — yet it does describe the result/reason-code shape, the gift-vs-engine origin split, and the enabled/included flags, which is the behavior an agent actually needs to interpret the response. The main residual gap is pagination mechanics and how the two state flags interact with calling the 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 reported as 0% (the single parameter is a nested input object), so the description carries the burden — but it only does so minimally with 'Args: {limit, before}', naming keys without adding format or bounds detail. The ordering hint ('newest first') is useful but duplicates what the nested limit property already says.

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 states a specific read of a specific resource: what Quick did autonomously on the user's jobs, broken out by 'origin gift' (free weekly find) and 'origin engine' (analysis, resume suggestions, tailored copy, cover letter, archive). The autonomous-work scope does distinguish it from user-facing activity tools, though it never names a sibling explicitly and leans on product jargon an agent may not resolve.

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 only implied: the reader infers 'call this to see what Quick produced on its own.' There is no when-to-use/when-not statement, no mention of the complementary write path (set_quick_autowork), and no disambiguation from other read tools like get_recent_activity or get_task_status that could plausibly cover similar ground.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.