Skip to main content
Glama

WritersLogic business agents

clause-tag

Rule-based clause tagging (obligation, prohibition, permission, condition, topic) — Tags each contract-style clause you supply with the modal force it expresses (obligation, prohibition, permission, recommendation) and topic cues (definition, condition, termination, payment, confidentiality, liability, governing law, notice, assignment), with the matched cue and its offset. For an agent that must triage many clauses before a human or model reads them. Fixed cue phrases only (plus

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": {
      "clauses": "<clauses>"
    },
    "name": "clause-tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
expectNoTags a clause must carry; a missing one fails.
clausesYesUp to 100000 characters in total.
extraCuesNoYour own cue phrases, matched as literal word sequences.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that matching is deterministic and literal ('Fixed cue phrases only'), that outputs include the matched cue and its offset, and that custom cues can be supplied — but it says nothing about the `expect` self-check behavior, failure handling, or ordering of returned tags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the tag taxonomy is genuinely informative, but the long parenthetical enumerations pad the text and the final sentence is cut off mid-phrase, leaving a dangling fragment. Trimming the topic list and completing the extraCues sentence would earn more.

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?

There is no output schema, yet the description covers the essential return shape (tag, matched cue, offset) and the tagging vocabulary, which is the main thing an agent needs. The gaps are the truncated tail and the unexplained `expect` verification parameter, which matter less for typical invocation.

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 100%, so all three parameters (clauses, extraCues, expect) are already documented in the schema, making 3 the baseline. The description only gestures at extraCues in a truncated fragment ('Fixed cue phrases only (plus') and adds no syntax or format detail beyond what the schema provides.

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 opens with a specific verb-plus-resource ('Rule-based clause tagging') and immediately enumerates the exact tag families produced (modal force and topic cues). An agent knows precisely what the tool returns — tags plus matched cue and offset — without opening the schema.

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?

Usage context is only implied by the clause 'For an agent that must triage many clauses before a human or model reads them,' which signals bulk pre-screening. There is no explicit when-not guidance, no mention of when a model-based reader is preferable, and no named alternative tool.

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