Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP

islamic_prayer_times_worldwide_monthly_calendars

Read-onlyIdempotent

Islamic Prayer Times Worldwide - Monthly Calendars: Real-time structured data extraction feed for Islamic Prayer Times Worldwide - Monthly Calendars.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "islamic_prayer_times_worldwide_monthly_calendars"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is low, yet the description only adds the word 'real-time' about data freshness. It says nothing about what the feed returns, pagination, rate limits, or coverage scope.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but entirely redundant — it duplicates the title and adds a boilerplate phrase. Conciseness here comes from under-specification rather than efficient communication.

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?

For a read-only extraction tool with no output schema, the description should say what data the records contain (timings, cities, month granularity). Instead it leaves the agent guessing about return content and scope despite the tool's simplicity.

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 100% for the single optional maxResults parameter, so the schema already documents its meaning. The description adds no additional semantics, but the baseline of 3 applies when the schema carries the parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name/title ('Islamic Prayer Times Worldwide - Monthly Calendars') and appends a generic phrase 'Real-time structured data extraction feed'. No specific verb like 'fetch', 'list', or 'return' clarifies the action, and nothing distinguishes it from the dozens of other scraper-style siblings.

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?

There is no guidance on when to use this tool, when not to, or what alternative to choose. The agent must infer usage entirely from the name.

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.