Skip to main content
Glama

Show the office's open work

get_outstanding_work
Read-onlyIdempotent

Use to list every open item for the office (or only the member's own with mine_only), oldest first, with its source. For a lawyer or staff member of a law office signed in to ESQ CoPilot for their office. Do not call it for a person looking for a lawyer (use search_attorneys) or for general legal questions.

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

Input Schema

NameRequiredDescriptionDefault
mine_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the result ordering ('oldest first') and that each item carries 'its source', plus the default-vs-mine_only scoping behavior. It stops short of describing the item shape or whether the list is paginated.

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?

Three compact sentences, front-loaded with the action and scope before the audience and exclusions. The audience sentence is slightly wordy ('signed in to ESQ CoPilot for their office') but carries genuine eligibility information, so nothing is truly wasted.

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 single-flag, read-only list tool with annotations covering safety and no output schema, the description supplies scope, ordering, item provenance, audience, and exclusions. The only gap is a hint at what fields each 'open item' contains and whether the list is bounded.

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?

Schema description coverage is 0%, so the description carries the burden for the single parameter, and it does: mine_only is explained as restricting the list to the member's own items. That fully defines the one flag's meaning beyond its name, though it doesn't state the default when omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('list every open item for the office'), adds the scoping modifier ('or only the member's own with mine_only'), and names a sibling it is not ('use search_attorneys'). An agent can distinguish this from search_attorneys without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit audience ('a lawyer or staff member of a law office'), explicit exclusions ('Do not call it for a person looking for a lawyer... or for general legal questions'), and names the alternative tool for the excluded case. This is close to a complete routing rule.

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.

Resources