Skip to main content
Glama

workquote_status

Checks whether your Cotlet.dev account and WorkQuote connection are ready, including account status and available credits.

Instructions

Check that your Cotlet.dev account and WorkQuote are ready: account, credits and WorkQuote connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does enumerate the three things being verified (account, credits, connection), which is real information beyond the name, and 'Check' implies a non-mutating read. It does not state whether the call has side effects, whether it consumes credits, what the result looks like when a check fails, or how errors surface — all material for a status tool with no output schema.

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 front-loaded sentence with the verb first and no filler. The trailing colon list ('account, credits and WorkQuote connection') slightly repeats 'your Cotlet.dev account and WorkQuote are ready', but it usefully enumerates the specific checks, so the redundancy is minor rather than wasteful.

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 simple zero-argument tool this covers the 'what', but a status/readiness check lives or dies on its return values, and with no output schema the description should indicate that it reports pass/fail per check (account, credits, connection) so the agent knows how to act on the result. That gap keeps it at adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, and the description correctly implies no input is needed. Nothing further is required of the description on this dimension.

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?

Uses a specific verb ('Check') plus the concrete subject of the check: Cotlet.dev account, credits, and WorkQuote connection readiness. That clearly separates it from the action-oriented siblings (open, click, type, read, close, guide), which manipulate WorkQuote rather than report readiness. It stops short of explicitly naming itself as the diagnostic/pre-flight tool versus the others, but the intent is unambiguous.

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?

The phrasing 'Check that ... are ready' implies a pre-flight or troubleshooting use case, so an agent can infer when to call it. However, there is no explicit when-to-use or when-not-to-use guidance, no mention of calling it before workquote_open or after a failure, and no reference to the sibling tools it should precede.

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