Skip to main content
Glama
Sign In
gpsem

gpsem

by puples
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Statistiques home du site

getSiteStats
Read-onlyIdempotent

Retrieve site statistics including published pages, scheduled pages, and indexing rate, aligned with the GPSEM dashboard.

Instructions

Statistiques home du site — Pages publiées, planifiées, taux d'indexation (aligné sur le dashboard GPSEM). — (GET /sites/{siteId}/stats)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteId": "<siteId>"
    },
    "name": "getSiteStats"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesID site encodé (hashid)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is established. The description adds that the statistics follow the GPSEM dashboard and that the call is a GET, which is useful but does not disclose deeper behavior such as auth needs or empty/error responses.

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?

The description is compact and the key information is front-loaded: what the stats cover, their dashboard alignment, and the endpoint. It slightly repeats the title with 'Statistiques home du site', but there is no meaningful bloat.

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 one-parameter, read-only tool with strong annotations and no output schema, the description names the main returned metrics and scopes the resource clearly. It is sufficient for correct invocation, though it could mention response format or authentication for full completeness.

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?

The schema describes siteId as 'ID site encodé (hashid)' with 100% coverage, so the parameter semantics are already fully documented. The description adds no parameter-level detail, but none is necessary here.

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 identifies the resource and specific metrics ('Pages publiées, planifiées, taux d'indexation') plus the GET endpoint, so an agent can tell it is a read-only stats tool for a site. It does not differentiate against sibling getters, which prevents a top score.

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?

The intended use is implied by the tool name and metric list, and the 'aligné sur le dashboard GPSEM' note gives some context. However, there is no explicit guidance about when to choose this over related dashboard/history/stat tools.

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

Deploy Server

Other Tools