Skip to main content
Glama

verify_doj

Read-onlyIdempotent

Verify DOJ policy citations like Prosecution Code §5.9 against the local DOJ corpus to confirm the reference exists; it checks citations only, not whether text supports a proposition.

Instructions

Verify a DOJ policy citation, e.g. Prosecution Code §5.9.

This checks the local DOJ corpus only. It is not a citator and does not verify that the paragraph supports a proposition.

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": {
      "citation": "<citation>"
    },
    "name": "verify_doj"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
categoryNo
citationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the description's added value is its explicit limits: local corpus only, no citator behavior, no proposition verification. That materially narrows what the agent can trust the result to mean. It still omits what happens for an unrecognized/ambiguous citation and whether the corpus may be stale.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and example, then the two scope caveats. No filler or repetition, and each sentence adds a distinct 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?

With no output schema, the description is the only place the return value could be characterized, yet it never says what "verify" yields (valid/invalid flag, matched text, error on miss). Combined with unexplained `lang`/`category` and silent failure behavior, the definition is workable but leaves an agent guessing at the result shape.

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%, so the description must carry parameter meaning. The citation example establishes the expected string format, which is the highest-value param detail here, but the `lang` and `category` parameters receive no explanation at all, leaving two of three parameters undocumented anywhere.

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?

States a specific verb+resource ("Verify a DOJ policy citation") and anchors it with a concrete example ("Prosecution Code §5.9"). Scope is narrowed to the local DOJ corpus, which implicitly separates it from general citation tools, but it never names verify_citation / verify_citations, so an agent still has to infer which verifier to pick.

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?

Provides genuine when-not guidance: "It is not a citator and does not verify that the paragraph supports a proposition," which steers the agent away from misuse for citator-style or proposition-support questions. It stops short of naming the tool that should be used instead for those cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.