Skip to main content
Glama

Mishkat (مِشكاة) Arabic Islamic lectures

Get a treasure

get_treasure
Read-onlyIdempotent

One treasure in full: its verbatim text, the explanation fields (summaries, not quotations), the exact segment range in its lecture and a timestamped link.

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": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "get_treasure"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the return shape and notably clarifying that explanation fields are 'summaries, not quotations' while the text is 'verbatim' — a distinction an agent cannot get from structured fields.

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?

A single front-loaded sentence with zero filler; the most important fact (one treasure, full content) leads and the return contents follow compactly.

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 no output schema, the description does a fair job of explaining returns, including the summary-vs-verbatim nuance. However, for a tool whose only inputs are a required type enum and an id, omitting any statement about how those two work together leaves a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 carry the burden, yet it says nothing about the two required parameters. It never explains that 'type' is an enum discriminator selecting among ten treasure categories nor how 'id' is scoped by type — the most error-prone part of invoking this tool.

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 uses a clear implicit retrieval verb with a specific resource ('one treasure in full') and enumerates exactly what comes back: verbatim text, explanation fields, segment range, and a timestamped link. The word 'One' plus 'in full' distinguishes single-item fetch from the sibling list/search tools, though no sibling is named explicitly.

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?

Usage is only implied: 'One treasure in full' suggests detail retrieval for a known item, contrasting with browse_treasures/search_treasures, but the description never states when to pick this over those alternatives or what prerequisite (a treasure id obtained elsewhere) is needed.

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