Skip to main content
Glama

Social Media Agency Directory

Directory statistics

directory_stats
Read-onlyIdempotent

Size and freshness of the directory: number of agencies, countries, cities and services, the date of the latest update, and links to how listings are verified and to the 2026 agency report.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
citiesYes
agenciesYes
servicesYes
countriesYes
report_urlNo
updated_atYes
attributionNo
how_we_verify_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description goes further by disclosing the content scope of the response, including the freshness timestamp and links to verification methodology and the 2026 agency report, which tells an agent this is a metadata/summary source rather than raw records.

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 sentence with the core framing ('size and freshness of the directory') front-loaded, followed by an enumeration of the returned fields. Every clause carries information; the only minor weakness is that the trailing list gets long and mixes return fields with link targets.

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, read-only statistics tool with a full output schema and complete annotations, the description supplies everything needed: what dimensions are measured, that freshness is included, and that provenance/verification links accompany the numbers. No invocation detail is left to guesswork.

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. Nothing in the description suggests hidden inputs, and the absence of parameters is consistent with a fixed statistics endpoint.

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 clearly states the resource and its contents: aggregate metrics about the directory (agencies, countries, cities, services, latest-update date, plus links to verification details and the 2026 report). It is a noun phrase rather than a verb+resource, and it never names a sibling to contrast with, but the aggregate/statistical nature makes it self-evidently distinct from get_agency or search_agencies.

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: an agent can infer this is the overview/orientation call for directory size and freshness. There is no explicit 'use when' statement, no mention of when not to use it (e.g. when you need per-record detail from search_agencies or list_services), and no named alternative.

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.

Resources