Skip to main content
Glama
Sign In
madeenan

madeenan

by itsmunzir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_evidence_bundle

Bundles Quran, Hadith, Tafsir, and dua search results with requested source lookups into a compact evidence collection for research; it does not decide religious rulings.

Instructions

Create a compact bundle of search results and requested source lookups.

This is an evidence collection helper. It does not decide a religious ruling.

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": {
      "query": "<query>"
    },
    "name": "create_evidence_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
indexesNo
referencesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses a useful scope limit (non-decisional helper) but says nothing about whether it performs live searches, whether it is read-only, cost/latency, or what happens when references fail to resolve.

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 short sentences with no filler, and the core purpose comes first. The scope disclaimer earns its place, though the overall brevity leaves obvious gaps rather than being genuinely complete.

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

Completeness2/5

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

With an output schema present, return values need no explanation, but a four-parameter tool with zero description coverage and no annotations needs more than three sentences. Key inputs and the aggregation behavior are left entirely unstated.

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 compensate; it partially does by linking "search results" to a query and "source lookups" to references. However, the 'indexes' and 'limit' parameters are never mentioned, leaving half the inputs 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 and resource ("Create a compact bundle") and clarifies the content as "search results and requested source lookups." The line "does not decide a religious ruling" implicitly separates it from review_evidence_claim, though the differentiation is indirect rather than an explicit contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage as an evidence-collection helper and hints at a when-not boundary by declaring it does not decide rulings, but it never states when to call this instead of search_islamic_sources or review_evidence_claim. The agent must infer that this aggregates results for later review.

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

Deploy Server

Other Tools