Skip to main content
Glama

فهرست پلتفرم‌های نوبت‌دهی

list_platforms
Read-onlyIdempotent

List supported Iranian doctor booking platforms with what each provides, plus sites checked but excluded and why. Use it to see coverage before searching doctors.

Instructions

List the supported Iranian doctor booking platforms, what each provides, and which sites were checked but excluded (and why).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and idempotency are covered structurally. The description adds genuinely new behavioral context by disclosing that the response includes rejected sites together with the reasons for exclusion — a non-obvious property of the return set that an agent would not guess. It does not mention ordering, size, or caching, but with annotations carrying the safety profile the bar is lower.

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 sentence with no filler, front-loaded on the primary result (supported platforms) and appending the secondary result (excluded sites and reasons). Every clause maps to something the caller gets back.

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

Completeness5/5

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

For a zero-parameter, read-only listing tool with no output schema, the description fully covers what the agent needs: the domain, the two categories of returned content, and confirmation that nothing is required as input. There is no meaningful gap left to fill.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly signals a parameterless catalog call rather than suggesting any filtering input.

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

Purpose5/5

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

A specific verb (List) plus a precisely scoped resource (supported Iranian doctor booking platforms) with the payload spelled out — what each provides and which sites were excluded and why. The subject matter (a platform catalog) is unmistakably distinct from the sibling tools get_doctor_details and search_doctor, which operate on individual doctors.

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: an agent can infer this is the discovery/overview call to make when it needs to know which platforms exist rather than look up a doctor. There is no explicit 'use this when...' clause, no statement about when not to call it, and no named alternative.

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