Georgia Commons

Check a quotation

verify_quote

Read-onlyIdempotent

Check whether a quotation appears word for word in a stored document (or one version of it), after normalizing whitespace, typographic quotes and dashes, [T]he-style alterations, amendment marks, and case. Use it before relying on a quotation.

Input Schema

Name	Required	Description
`id`	Yes	The document id (or any written form of one).
`quote`	Yes	The quotation to check, at least 12 characters.
`version`	No	A version id to check; default the current version, then earlier ones.

Output Schema

Name	Required	Description	Default
`id`	Yes
`in`	No
`chars`	Yes
`found`	Yes
`md_url`	Yes
`current`	No
`version_id`	No
`occurrences`	Yes
`canonical_url`	Yes
`version_label`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedNov 6, 2026

changedInput schema / properties / id / description

Previous value: -"The document's id, as search and fetch return it: code:44-7-34, bill:2025-2026/hb136, opinion:S26A0060, meeting:2026-02-05/house-rules."New value: +"The document id (or any written form of one)."

addedInput schema / properties / id / maxLength
```
Added value: +300
```

changedInput schema / properties / quote / description

Previous value: -"The quotation to check, at least 12 characters and at most 4,000."New value: +"The quotation to check, at least 12 characters."

changedInput schema / properties / quote / minLength
```
Previous value: -1New value: +12
```

addedInput schema / properties / version

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "A version id to check; default the current version, then earlier ones.",
+  "title": "Version"
+}

addedOutput schema / properties / canonical_url

Added value: +{
+  "title": "Canonical Url",
+  "type": "string"
+}

addedOutput schema / properties / current

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Current"
+}

addedOutput schema / properties / found

Added value: +{
+  "title": "Found",
+  "type": "boolean"
+}

addedOutput schema / properties / in

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "In"
+}

addedOutput schema / properties / md_url

Added value: +{
+  "title": "Md Url",
+  "type": "string"
+}

removedOutput schema / properties / source_field

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "title": "Source Field"
-}

removedOutput schema / properties / url

Removed value: -{
-  "title": "Url",
-  "type": "string"
-}

removedOutput schema / properties / verified

Removed value: -{
-  "title": "Verified",
-  "type": "boolean"
-}

addedOutput schema / properties / version_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Version Id"
+}

addedOutput schema / properties / version_label

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Version Label"
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "url",
-  "verified",
-  "occurrences",
-  "source_field",
-  "chars"
-]New value: +[
+  "id",
+  "found",
+  "occurrences",
+  "chars",
+  "canonical_url",
+  "md_url"
+]

changedOutput schema / title

Previous value: -"VerifyResult"New value: +"VerifyOutput"

Changed5 schema fields changedOct 27, 2026

addedInput schema / properties / id / description

Added value: +"The document's id, as search and fetch return it: code:44-7-34, bill:2025-2026/hb136, opinion:S26A0060, meeting:2026-02-05/house-rules."

addedInput schema / properties / id / minLength
```
Added value: +1
```

addedInput schema / properties / quote / description

Added value: +"The quotation to check, at least 12 characters and at most 4,000."

addedInput schema / properties / quote / maxLength
```
Added value: +4000
```
addedInput schema / properties / quote / minLength
```
Added value: +1
```

First observedSep 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description earns credit for disclosing non-obvious matching behavior beyond the annotations: normalization of whitespace, typographic quotes and dashes, [T]he-style alterations, amendment marks, and case, plus the current-version-then-earlier-versions fallback. It does not describe the result shape, but an output schema exists to carry that.

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?

Two sentences, front-loaded with the core check and its normalization caveats, then a short usage clause. Slightly clunky with the bracketed '[T]he-style alterations' fragment and the trailing '(or one version of it)', but nothing is genuinely redundant.

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 read-only verification tool with rich annotations, a fully documented schema, and an output schema, the description covers what an agent needs: what is compared, how normalization affects matching, and the version scope. It could say more about what a failed match implies (e.g. that amendment marks make near-misses expected), but no essential calling information is missing.

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% and all three parameters are documented in the schema, including the version fallback and the 12-character quote minimum. The description adds no syntax or format detail for id, quote or version beyond what the schema already states, so the baseline of 3 applies.

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: 'Check whether a quotation appears word for word in a stored document (or one version of it)'. It also scopes the comparison semantics, so an agent can tell this apart from the sibling retrieval tools (search, fetch, describe_site, get_coverage) 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 Guidelines4/5

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

'Use it before relying on a quotation' gives a clear usage context, and the verification framing makes the intent unambiguous. It stops short of naming exclusions or pointing at an alternative path (e.g. what to do when the quote is not found, or when to use search instead), so it lands at 4 rather than 5.

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

All Georgia Commons tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?