Skip to main content
Glama

Chinng AI-Agent Portal

portal_popular

Return the most retrieved portal pages.

Args: window: rolling window such as "24h", "7d", "30d" or "90d". category: optional category prefix such as "news" or "security". limit: number of results (default 10, max 100 on the analytics service).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
windowNo24h
categoryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden. It hints at backend behavior by noting the limit is capped at 100 "on the analytics service", but never states that the call is read-only, whether auth or specific scopes are required, what latency/aggregation period applies, or anything about ordering ties.

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 purpose sentence is front-loaded and the remaining text is a compact, scannable per-parameter block with no filler. The Python-docstring "Args:" formatting is slightly awkward for a tool description but costs little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and all three parameters get some coverage. However, for a no-annotation tool the description should say more about the read-only/analytics nature and any service limits beyond the one passing mention of the 100 cap.

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?

Schema description coverage is 0%, so the description must supply parameter meaning, and it does: it names all three parameters and gives concrete window values ("24h", "7d", "30d", "90d"), shows category as a prefix with examples ("news", "security"), and states the limit default and hard max. It stops short of declaring the default window and the null-category behavior, which are only visible in the schema.

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?

"Return the most retrieved portal pages" names a specific operation (ranking by retrieval count) on a specific resource (portal pages), so an agent can tell this is a popularity/analytics query rather than a search or listing call. It does not explicitly contrast itself with siblings such as portal_search or portal_list, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool instead of portal_search, portal_list, or portal_changes, and no prerequisites or exclusions are given. The only hint of context is the word "retrieved", leaving the agent to infer that this is a popularity-ranking endpoint.

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