Skip to main content
Glama

What needs my office's attention today?

get_office_briefing
Read-onlyIdempotent

Use when a lawyer or staff member asks "what needs my attention today?". Returns the office's real list: overdue tasks, inquiries waiting for a reply, appointments, documents to review and prepared drafts, each with why it is listed and where it came from, plus what is not connected. Never add items, deadlines or advice of your own. 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_office_briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo
for_dateNo
matter_idNo
mine_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely useful behavior: every item carries 'why it is listed and where it came from', the response discloses 'what is not connected', and it forbids the agent from inventing items, deadlines or advice. It does not discuss ordering, volume, or how the default date window is chosen, so not a 5.

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?

Front-loaded with the trigger condition, then the returned content, then the guardrail, then the exclusions — a sensible order with no filler sentences. The eligibility clause ('for a lawyer or staff member of a law office signed in to ESQ CoPilot for their office') is slightly redundant with the opening sentence but still earns its place.

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 no-required-parameter read tool the core purpose is well covered, and the description compensates for the missing output schema by describing the payload's contents and provenance. However, with no output schema and 0% parameter documentation, the four optional filters remain unexplained, leaving a real gap in a tool whose value comes from filtering.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description must carry the burden, and it does not. Nothing explains the ten-value category enum, the for_date format/default (presumably today), what matter_id scopes, or how mine_only differs from the office-wide default — all left for the agent to guess.

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?

States a concrete trigger ('what needs my attention today?') and enumerates what comes back: overdue tasks, inquiries awaiting reply, appointments, documents to review, prepared drafts, each with provenance plus uncovered areas. It also names the audience (lawyer/staff of an office signed in to ESQ CoPilot), which separates it from person-facing tools like search_attorneys.

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?

Explicit when-to-use (a lawyer or staff member asking what needs attention today), explicit when-not (someone looking for a lawyer, or general legal questions), and it names the alternative tool, search_attorneys, for the excluded case. Little is left to inference.

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