Skip to main content
Glama

ElkassabgiData Family Status

get_family_status
Read-only

Live status of the whole ElkassabgiData family - HF, Econ and IP: each library's headline stats and data currency, read live. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safe-read profile, so the bar is lower. The description adds 'read live' (freshness expectation) and 'Free' (cost context), which is genuinely useful behavioral context, but it says nothing about latency, rate limits, or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words; the scope (HF, Econ, IP) and content (headline stats, currency) come first. The dash notation and abbreviations ('HF', 'IP') are slightly terse but efficient.

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?

With no output schema, the description must convey the return shape, and it does: 'each library's headline stats and data currency'. For a simple read-only status endpoint with no parameters, that is close to enough, though it doesn't hint at structure or granularity of the returned stats.

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; the baseline for a 0-param tool is 4. The description correctly implies the call is unparameterized by describing a whole-family snapshot.

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?

States a concrete verb+resource ('Live status of the whole ElkassabgiData family') and enumerates the scope covered (HF, Econ and IP), which sets it apart from the per-library siblings. It doesn't explicitly name the siblings it replaces (e.g., get_data_freshness, get_auth_status), so differentiation is implied rather than spelled out.

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 implied by 'the whole family' - a roll-up overview across all three libraries - but there is no explicit when-to-use or when-to-prefer-a-narrower-sibling guidance. Given overlapping siblings like get_data_freshness and get_auth_status, the absence of routing guidance is a real gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.