Skip to main content
Glama
apify-insights

apify-insights

by Devansh-365

Connection status

auth_status
Read-onlyIdempotent

Verifies whether the Apify API token is valid and which account it belongs to, and checks the Console session state for money data; use it when another tool returns an authentication error.

Instructions

Whether the Apify API token works (and for which account) and the state of the Console session used for money data. Call this when another tool returns an auth error.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds real context beyond that: it discloses that two separate auth surfaces are checked (API token and Console session) and that the session governs money data, which is the kind of diagnostic scope an agent needs. It stops short of describing the response shape, which is the remaining gap given no output 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, zero filler, and the scope statement is front-loaded ahead of the invocation trigger. Every clause carries information an agent would otherwise have to guess.

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 zero-parameter diagnostic with no output schema, the description covers what is checked and when to invoke it, which is close to sufficient. It would be stronger if it indicated what the agent should do with a failed token versus a failed session, since the caller has no schema to infer the response from.

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; baseline applies. No misleading parameter talk is present.

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 the two things the tool inspects — the Apify API token's validity and associated account, plus the Console session state used for money data. That is specific enough to distinguish it from every sibling (all data/analytics tools), though it is phrased as a statement of returned facts rather than a verb+resource, so the action ('check/diagnose') is implied.

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?

It gives an explicit trigger: 'Call this when another tool returns an auth error.' That is a clear, actionable when-to-use rule. It does not cover the inverse (when not to bother) or note that it can be used proactively before a money-data call, but for a diagnostic tool the single trigger is the essential guidance.

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