Skip to main content
Glama
scamverifyai

ScamVerify

get_status

Read-onlyIdempotent

Check the operational status of ScamVerify API services, including phone, URL, text, email, document lookups, database, and AI inference components.

Instructions

Check the operational status of ScamVerify API services. Returns health status for each component (phone, URL, text, email, document lookups, database, AI inference). No authentication required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and handler implementation for the 'get_status' tool, which fetches API status without authentication.
    // 10. get_status
    server.tool(
      'get_status',
      'Check the operational status of ScamVerify API services. Returns health status for each component (phone, URL, text, email, document lookups, database, AI inference). No authentication required.',
      {},
      {
        title: 'Get Service Status',
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false,
      },
      async () => {
        try {
          // Status endpoint does not require auth
          const res = await fetch(`${BASE_URL}/api/v1/status`, { method: 'POST' });
          const data = await res.json();
          return jsonResult(data);
        } catch (err) {
          return errorResult(err instanceof Error ? err.message : 'Failed to get status');
        }
      },
    );
Behavior4/5

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

Annotations cover safety (readOnlyHint, destructiveHint), so description adds valuable behavioral context: 'No authentication required' and detailed return structure (health status for each component). No contradictions with annotations.

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 efficient sentences with zero waste. Front-loaded with the action verb, followed by return value description and authentication note. Every clause earns its place.

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 health check tool, description is complete: explains purpose, discloses authentication requirements, and enumerates all service components in the response despite lack of output schema. Aligns components with sibling tool capabilities.

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?

Zero parameters present, warranting baseline score of 4 per rubric. No parameters require semantic explanation.

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?

Specific verb 'Check' with clear resource 'operational status of ScamVerify API services'. Explicitly distinguishes from content-checking siblings (check_phone, check_url, etc.) by stating it monitors the API components themselves (database, AI inference) rather than user-submitted content.

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?

Provides clear context through 'No authentication required' and lists the specific components returned (phone, URL, text, email, document, database, AI). Lacks explicit 'when not to use' exclusions, though the component list implicitly contrasts with sibling tools.

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/scamverifyai/scamverify-mcp'

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