Skip to main content
Glama
imviky-ctrl

Tickerr — Live AI Tool Status & API Pricing

get_tool_status

Check live operational status, uptime percentage, and response time for any AI tool by providing its slug. Data updates every 5 minutes from independent monitoring infrastructure.

Instructions

Get live operational status, uptime percentage, and response time for any AI tool. Checks every 5 minutes from independent infrastructure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesTool slug — e.g. "chatgpt", "claude", "cursor", "github-copilot", "gemini"

Implementation Reference

  • The async handler function that executes the get_tool_status tool logic: fetches tool status from the API, formats uptime, response time, last checked time, and active incident info into a text response.
      async ({ slug }) => {
        const d = await fetchJSON<ToolStatus>(`/tools/${slug}/status`)
        const uptime = (label: string, pct: number | null) =>
          pct !== null ? `${label} uptime: ${pct}%` : `${label} uptime: no data`
    
        const lines = [
          `**${d.tool.name}** — ${d.status.toUpperCase()}`,
          d.response_ms !== null ? `Response time: ${d.response_ms}ms` : null,
          d.checked_at ? `Last checked: ${new Date(d.checked_at).toUTCString()}` : null,
          uptime('30-day', d.uptime_30d),
          uptime('90-day', d.uptime_90d),
        ].filter(Boolean) as string[]
    
        if (d.active_incident) {
          const i = d.active_incident
          lines.push('', `⚠️ ACTIVE INCIDENT: ${i.title}`, `  Severity: ${i.severity}`, `  Since: ${new Date(i.started_at).toUTCString()}`)
        }
    
        lines.push('', `Full status page: https://tickerr.ai/status/${slug}`)
        return { content: [{ type: 'text' as const, text: lines.join('\n') }] }
      }
    )
  • Input schema for get_tool_status: expects a single 'slug' string parameter describing which AI tool to check status for.
    { slug: z.string().describe('Tool slug — e.g. "chatgpt", "claude", "cursor", "github-copilot", "gemini"') },
  • src/index.ts:83-108 (registration)
    Registration of the 'get_tool_status' tool on the MCP server with its description, input schema, and handler.
    server.tool(
      'get_tool_status',
      'Get live operational status, uptime percentage, and response time for any AI tool. Checks every 5 minutes from independent infrastructure.',
      { slug: z.string().describe('Tool slug — e.g. "chatgpt", "claude", "cursor", "github-copilot", "gemini"') },
      async ({ slug }) => {
        const d = await fetchJSON<ToolStatus>(`/tools/${slug}/status`)
        const uptime = (label: string, pct: number | null) =>
          pct !== null ? `${label} uptime: ${pct}%` : `${label} uptime: no data`
    
        const lines = [
          `**${d.tool.name}** — ${d.status.toUpperCase()}`,
          d.response_ms !== null ? `Response time: ${d.response_ms}ms` : null,
          d.checked_at ? `Last checked: ${new Date(d.checked_at).toUTCString()}` : null,
          uptime('30-day', d.uptime_30d),
          uptime('90-day', d.uptime_90d),
        ].filter(Boolean) as string[]
    
        if (d.active_incident) {
          const i = d.active_incident
          lines.push('', `⚠️ ACTIVE INCIDENT: ${i.title}`, `  Severity: ${i.severity}`, `  Since: ${new Date(i.started_at).toUTCString()}`)
        }
    
        lines.push('', `Full status page: https://tickerr.ai/status/${slug}`)
        return { content: [{ type: 'text' as const, text: lines.join('\n') }] }
      }
    )
  • Generic helper function fetchJSON used by the handler to call the tickerr API for tool status data.
    async function fetchJSON<T>(path: string): Promise<T> {
      const res = await fetch(`${BASE_URL}${path}`, { headers: { 'User-Agent': UA } })
      if (!res.ok) {
        const text = await res.text().catch(() => '')
        throw new Error(`tickerr API ${res.status}: ${text.slice(0, 200)}`)
      }
      return res.json() as Promise<T>
    }
  • TypeScript interface ToolStatus defining the shape of the API response used by the handler.
    interface ToolStatus {
      tool: { slug: string; name: string; vendor: string; homepage_url: string | null }
      status: 'operational' | 'down' | 'unknown'
      is_up: boolean | null
      response_ms: number | null
      checked_at: string | null
      uptime_30d: number | null
      uptime_90d: number | null
      active_incident: { id: string; title: string; severity: string; started_at: string; source: string } | null
    }
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses update frequency (checks every 5 minutes) and data source (independent infrastructure), adding value beyond schema.

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?

Two sentences, no fluff. Front-loaded with purpose, additional info in second sentence. Every sentence earns its place.

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

Completeness4/5

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

For a simple tool with 1 param and no output schema or annotations, description covers purpose, update frequency, and source. Lacks return format details but sufficient given 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?

Input schema has 100% description coverage with examples for slug. Description does not add further meaning beyond what schema already provides, baseline 3.

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?

Description clearly states the verb 'Get' and the resource: live operational status, uptime percentage, and response time for any AI tool. This distinguishes it from siblings like compare_pricing or get_incidents.

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?

Implied usage: use it to get operational status for a specific tool slug. No explicit when-to-use or alternatives mentioned, nor exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/imviky-ctrl/tickerr-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server