Skip to main content
Glama

Add a task for the office

create_office_task
Idempotent

Use when the member asks to add a task. Pass a new create_key each time; the same key returns the same task. A due date is the office's own date, never a court deadline. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "create_key": "<create_key>",
      "title": "<title>"
    },
    "name": "create_office_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
due_atNo
priorityNo
matter_idNo
create_keyYes
owner_member_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the write and idempotency profile is structured data. The description's added value is the concrete retry contract ('pass a new create_key each time; the same key returns the same task') and the due-date semantics (office's own date, never a court deadline), but it says nothing about what is created or returned. Useful but partial beyond annotations.

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?

Four short sentences, front-loaded with the trigger and idempotency rule before the audience and exclusion caveats. Every sentence carries information; the audience sentence is the only slightly heavyweight clause but it earns its place as a routing constraint.

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 6-parameter mutation with no output schema, the definition covers the trigger, idempotency, one date field and audience scope, but leaves half the parameters unexplained and never says what a successful call produces (task id, due-date default, owner default when owner_member_id is omitted). Adequate, not complete.

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 0% across 6 parameters, so the description must compensate and only partly does: it covers create_key (regeneration and idempotency) and due_at (office-local date, non-court). title, priority, matter_id and owner_member_id carry no meaning in either place, and the enum for priority is unexplained.

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 specific verb and resource ('add a task') plus a concrete trigger ('Use when the member asks to add a task'), and explicitly names the sibling it is not (search_attorneys). An agent can tell it apart from the other office tools without opening a 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?

Gives explicit when-to-use ('member asks to add a task'), who-for scoping (lawyer or law-office staff signed in to ESQ CoPilot), and two explicit exclusions routing to alternatives (search_attorneys; general legal questions). Little inference is left.

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