Skip to main content
Glama

review_evidence_claim

Check whether supplied evidence is relevant to a claim without verifying its truth; use it as a basic checklist and remind users to include source references and seek qualified interpretation.

Instructions

Review whether supplied evidence is relevant to a claim without verifying truth.

This tool performs a basic evidence checklist. It does not certify a claim, issue a fatwa, or verify religious meaning. Include source references in the evidence list and ask a qualified scholar for interpretation.

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": {
      "claim": "<claim>",
      "evidence": "<evidence>"
    },
    "name": "review_evidence_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYes
evidenceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose the key limitation (a basic checklist, not certification or verification) and an input-content expectation (include source references), which is real value, but it says nothing about how strict the relevance judgment is, what happens with unverifiable or empty evidence, or any sensitivity of the output.

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?

Three tight sentences, front-loaded with the core action and its main limitation. The fatwa/scholar disclaimer is slightly defensive but genuinely routes the agent away from misuse, so it earns its place.

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?

An output schema exists, so return-value detail is unnecessary here, and the tool is simple (two parameters, one string and one string array). The description covers purpose, refusals, and handoff, leaving only the undefined `claim` parameter and relevance criteria unspecified.

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% for both parameters, so the description must compensate. "Include source references in the evidence list" does add meaning beyond the raw array-of-strings schema, but the `claim` parameter is never described, and nothing explains the expected granularity or format of evidence entries.

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?

The description gives a specific verb and resource: review whether supplied evidence is relevant to a claim, plus a clear scope limiter ("without verifying truth"). It does not reference any sibling tool (e.g. find_quote_source or lookup_hadith_reference) to distinguish this review step from source-retrieval tools, so it stops short of a 5.

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 states when-not conditions explicitly: it does not certify a claim, issue a fatwa, or verify religious meaning, and directs the agent to a qualified scholar for interpretation. What's missing is a positive routing statement naming the alternative tool for when the agent actually needs verification or source lookup.

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