Skip to main content
Glama

Nalegalu MCP

by io.github.nalegaluorg
OverviewDiscussionsAdmin

verify_quote

Read-only

Check whether a supplied quote appears in a SAOS judgment.

    Use only after resolving the judgment to a saos_id. This validates
    wording, not whether the quote supports a legal conclusion. Pass the
    saos_id (from search_case_by_signature or related_cases) and
    the fragment as quoted. One call replaces paging through the full
    text: verdict is "exact" (verbatim after normalizing whitespace,
    quote marks and dashes), "near_match" (best passage plus similarity
    score — compare it against the claim), or "not_found" (treat the
    quote as fabricated or misattributed). If ok=false with a fallback
    hint, fetch saos_url with your own web tools instead of retrying.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quoteYes
saos_idYes
min_similarityNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, openWorld), and the description goes well beyond them: it enumerates the three verdict states with their meanings, explains the normalization rules behind 'exact', and instructs what to do on ok=false with a fallback hint. This is unusually rich behavioral disclosure.

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?

Front-loaded with the core purpose, then prerequisites, then verdict semantics, then fallback behavior — a sensible order with no filler. It is a little dense across five sentences for a three-parameter tool, but every clause conveys actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return structure need not be documented, yet the description still explains the verdict vocabulary and the ok/fallback-hint protocol. Combined with the prerequisite and normalization notes, an agent has everything needed to call it correctly and interpret the result.

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 0%, so the description carries the burden. It documents saos_id (integer id sourced from search_case_by_signature or related_cases), quote formatting ('as quoted', with whitespace/quote-mark/dash normalization), and implies the similarity score that min_similarity controls. min_similarity itself is never named or explained, which is the one gap.

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 supplied quote appears in a SAOS judgment.' It also articulates scope precisely — 'validates wording, not whether the quote supports a legal conclusion' — which distinguishes it from research/argument-oriented siblings. An agent can tell it apart from get_case or search_case_by_signature without opening any 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 an explicit precondition ('Use only after resolving the judgment to a saos_id'), names where the saos_id comes from (search_case_by_signature or related_cases), and states what the tool is not for. It also handles the failure path: retry versus falling back to saos_url with the agent's own web tools.

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

All Nalegalu MCP toolsInspect
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