Skip to main content
Glama

LinkVet

Verify a quote appears on a page

verify_quote
Read-onlyIdempotent

Before you attribute a quote to a source, check that the exact words really appear on that page. Returns found (true only for verbatim or punctuation/case-only differences), match_type (exact | normalized | near | partial | none), similarity 0-1, the closest_match text actually on the page with surrounding context, and safe_to_quote. Use closest_match to correct misquotes.

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": {
      "url": "<url>",
      "quote": "<quote>"
    },
    "name": "verify_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage that supposedly contains the quote
quoteYesThe quoted text to look for (3-3000 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), but the description adds meaningful behavior: the precise threshold for found=true (verbatim or punctuation/case-only differences) and the enumerated match_type values including 'near' and 'partial'. It does not mention limits such as page size, fetch failures, or rate constraints, which is the main remaining gap.

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 tight sentences, front-loaded with the decision the agent must make before quoting. Every clause carries information — the threshold, the return fields, and the corrective action — with no repetition of the schema or title.

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?

With no output schema, the description compensates by enumerating the returned fields (found, match_type, similarity, closest_match, safe_to_quote) and their meaning. For a two-parameter read-only verification tool, an agent has everything needed to call it and interpret the result.

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 coverage is 100% and both parameters are already documented with their roles and the 3-3000 char bound. The description reinforces that the quote must be the exact words and the URL is the supposed source, but adds no syntax or format detail beyond the schema, 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?

The description names a specific verb and resource — check that exact quote words appear on a given page — and frames it as a verification step before attribution. That is clearly distinct from siblings like read_page or check_url, which fetch or validate a page rather than verify quoted text against it.

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?

It gives a clear triggering context ('Before you attribute a quote to a source') and a follow-up action ('Use closest_match to correct misquotes'). It does not explicitly name an alternative tool or a when-not-to-use case, so it stops short of full routing guidance.

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