Skip to main content
Glama

eksisozluk_health

Checks whether eksisozluk.com is reachable right now, returning status ok, blocked, or error with the HTTP code and probed URL so you can confirm access before fetching any content.

Instructions

Check whether eksisozluk.com is reachable right now.

Returns status ok (HTTP 200), blocked (HTTP 403/429 — bot wall or rate limit) or error, plus the HTTP status and the probed URL. One polite request; it does not fetch any listings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does it well: it enumerates the three status outcomes, explains what 403/429 mean (bot wall or rate limit), discloses the returned fields, and states the cost profile of a single polite request with no listing fetches. It stops short of mentioning timeouts or whether a 'blocked' result implies a cooldown before retrying other tools, which would complete the picture.

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?

The purpose is front-loaded in the first line, followed by a compact paragraph covering outcomes and cost. Every sentence adds information: the status enumeration, the meaning of 403/429, and the 'no listings' scoping note each do distinct work.

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?

This is a simple zero-parameter diagnostic with an output schema, and the description goes beyond the schema by glossing the status semantics. Nothing an agent needs in order to call it correctly — what it does, what it returns, and what it costs — is absent.

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 the baseline is 4 and there is nothing for the description to compensate for. It correctly adds no parameter prose, keeping the text focused on behavior.

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?

The first sentence names a specific verb and resource: check whether eksisozluk.com is reachable right now. The closing clause 'it does not fetch any listings' explicitly separates it from the content-oriented siblings (get_topic, debe, search_topics), so an agent can tell what class of tool this is without opening the schema.

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

Usage Guidelines4/5

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

Usage is clearly implied as a pre-flight/diagnostic check, and the note that it fetches no listings contrasts it with the content siblings. What's missing is an explicit directive such as 'call this before other eksisozluk tools if you suspect the site is down or rate limiting you', so the when-to-use is inferred rather than stated.

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