Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP

turkey_on_duty_pharmacies_nobetci_eczane_daily

Read-onlyIdempotent

Turkey On-Duty Pharmacies (Nobetci Eczane) - Daily: Real-time structured data extraction feed for Turkey On-Duty Pharmacies (Nobetci Eczane) - Daily.

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

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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only 'real-time' and 'daily' cadence signals, which is modest value; it says nothing about geographic coverage (all provinces vs. a single city), freshness lag, or result volume behavior.

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

Conciseness3/5

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

The description is short, but nearly half of it is a verbatim repetition of the title after the colon. It is front-loaded with the resource name, yet the two clauses convey the same information rather than building on each other.

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 feed tool with no output schema, the description should at minimum indicate what the returned records look like or what scope of results to expect. It instead repeats the title, leaving return shape and coverage unstated, which is a real gap given there is no output schema to fall back on.

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?

There is a single optional parameter (maxResults) with 100% schema description coverage, so the schema fully documents it. The description adds no meaning about the parameter, which is acceptable given the high coverage baseline.

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

Purpose3/5

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

The description identifies the resource (Turkey on-duty pharmacies / Nobetci Eczane, daily), which does distinguish it from siblings like fuel prices or earthquake feeds. However, the verb is jargon ('structured data extraction feed') and the second clause simply restates the title verbatim, so the agent learns what data domain it is but not concretely what the call does.

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 when-to-use guidance, no prerequisites, and no mention of alternatives or when not to call it. The agent must infer entirely from the name that this is the tool for on-duty pharmacy lookups.

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.