Skip to main content
Glama

bim_health

Checks whether bim.com.tr is reachable right now, returning OK, blocked, or error status plus the HTTP code and probed URL.

Instructions

Check whether bim.com.tr 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": "bim_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.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the three possible outcomes (ok/blocked/error), decodes 403/429 as a bot wall or rate limit, and states the request is a single polite call that does not fetch listings. Missing only guidance on retry/backoff behaviour after a 'blocked' result.

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?

Three short lines: purpose first, return values second, scope disclaimer last. Every sentence carries information an agent would otherwise have to guess, and nothing is padded.

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 probe with an output schema already documenting the return shape, the description supplies everything else needed: what is probed, the status vocabulary, and the guarantee that no listings are fetched. No meaningful gap remains.

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 of 4 applies; the description correctly adds no parameter chatter and instead spends its words on outcomes.

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 names a specific verb and resource: 'Check whether bim.com.tr is reachable right now.' The closing clause 'it does not fetch any listings' implicitly separates it from the product/category siblings, so an agent can tell this is a connectivity probe rather than a data-retrieval tool, though no sibling is named outright.

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. The tool is clearly a pre-flight reachability check, and the note 'One polite request; it does not fetch any listings' sets a scope boundary, but the description never states when to prefer this over just calling a data tool or what to do on a 'blocked' result.

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