Skip to main content
Glama
Sign In

mu

by mu.micro
OverviewDiscussionsAdmin

References islam

islam_references

Search Quran, hadith and names of Allah by meaning through Reminder. Returns source passages and original metadata, never a generated answer. Use full source context before interpretation; missing authenticity metadata is not a grading.

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": "islam_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA question in plain language, e.g. "what is said about patience"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations supply only a title, so the description carries the full burden. It does disclose genuinely useful behavior: results are source passages with original metadata and never a generated answer, and missing authenticity metadata should not be read as a quality signal. It does not state read-only safety, result limits, ordering, or pagination, leaving meaningful gaps for a retrieval tool.

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 the capability front-loaded and no padding. Some phrasing is awkward ('through Reminder', 'is not a grading') and slightly obscures meaning, but nothing is redundant.

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

Completeness3/5

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

With one parameter and no output schema, the description reasonably explains that returns are raw passages plus metadata. However, it omits what an agent needs to choose this tool over its many near-siblings and says nothing about result volume or ranking.

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 the single query parameter is documented with an example, so baseline is 3. The phrase 'by meaning' hints at semantic rather than keyword matching, which adds a little value beyond the schema, but no further query-construction guidance is given.

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 set: search Quran, hadith and names of Allah by meaning, and clarifies results are passages rather than generated answers. It is weaker on differentiation, since sibling tools islam_search, islam_verse, islam_saying and prayer_search clearly overlap and are never mentioned.

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

Usage Guidelines2/5

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

The only guidance given ('use full source context before interpretation') concerns how to read results, not when to pick this tool over the many overlapping islam_* and prayer_* siblings. No exclusions, prerequisites, or alternative routing are provided.

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

All mu 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