Skip to main content
Glama

Mandate Law: legal counsel for AI products

Start a conflict check

conflict_check

Free. Required before any product details are shared. Names only: the client company, the human principal, other people involved, and any adverse, competing, or counterparty companies. The attorney reviews every check.

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": {
      "client_name": "<client_name>",
      "contact_name": "<contact_name>"
    },
    "name": "conflict_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_nameYes
contact_nameYesThe human principal.
other_peopleNo
adverse_or_related_partiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the call is free, that it is a mandatory gate ahead of sharing product details, and that a human attorney reviews every submission — a real workflow consequence not visible in readOnlyHint=false or destructiveHint=false. It stops short of saying what the caller receives back or whether duplicate submissions create separate reviews, which matters given there is 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?

Four terse sentences, each carrying a distinct fact — cost, timing requirement, content restriction, review outcome. Slightly front-loads "Free" rather than the more decision-critical precondition, but there is no filler to cut.

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 four-parameter write tool with no output schema, the description covers purpose, gating condition, permitted content, and the human-review consequence, which is enough to call it correctly. The main residual gap is the response outcome after submission, which the absence of an output schema leaves entirely unstated.

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 coverage is only 25% (only contact_name is documented), but the description compensates by mapping each parameter to plain business meaning: client company, human principal, other people involved, and adverse/competing/counterparty companies. "Names only" also constrains the value format for all four fields, adding guidance the schema's maxLength rules do not convey.

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 title plus description make clear this initiates a conflict check and enumerates exactly what goes into it: client company, human principal, other people, and adverse/competing/counterparty companies. It is specific about the resource and the content, but never contrasts itself with siblings such as check_scope or request_engagement, so an agent must infer the boundary.

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

Usage Guidelines4/5

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

"Required before any product details are shared" is a concrete trigger condition, and "Names only" is a clear content restriction that tells the agent what must not be sent. There is no explicit when-not guidance or named alternative for related checks, which keeps it short of a 5.

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