Skip to main content
Glama

Refora

Top cited domains, all workspaces

get_top_cited_domains
Read-onlyIdempotent

The domains AI models cite most across ALL workspaces in the organization. Aggregate view for multi-workspace orgs.

Use when the user wants org-level source analysis -- phrases like 'across all workspaces', 'org-wide sources', 'top domains overall', or 'which sites dominate'. For one workspace, use get_citation_sources.

Example: 'Which domains are cited most across all our brands?'

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_top_cited_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to look, counted back from end_date (default today). Default 30, max 90. Ignored when start_date is given. Prompts are re-run on a schedule, so a window shorter than a week can be empty.
end_dateNoOptional end of the window, as an ISO date (YYYY-MM-DD). Default today. Cannot be in the future.
start_dateNoOptional explicit start of the window, as an ISO date (YYYY-MM-DD). A full ISO datetime is accepted and its date is used. Overrides days.
domain_limitNoHow many domains to list. Default 15, max 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile carries itself. The description adds the meaningful behavioral fact that results are aggregated across all workspaces rather than scoped, which the annotations cannot convey. It stops short of describing the returned structure or the empty-window caveat that the schema mentions.

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?

Purpose is front-loaded in the first sentence, followed by usage triggers, the alternative, and an example. Every element is relevant, though the closing example query largely restates the trigger phrases already listed and is slightly redundant.

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-required-parameter, read-only aggregate with fully documented inputs, the description covers purpose, scope, and routing to the sibling alternative. The one gap is return shape: there is no output schema, so an agent gets no hint about what the domain list entry contains (rank, citation count, etc.), though this is a minor omission for a simple list tool.

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?

Schema description coverage is 100%, and every parameter (days, start_date, end_date, domain_limit) is documented in detail in the schema, including the days/start_date precedence and the short-window emptiness warning. The description adds no parameter-level meaning, which is acceptable given the schema does the heavy lifting, but nothing extra is contributed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('domains AI models cite most') plus an explicit scope ('across ALL workspaces in the organization'), and explicitly frames it as the aggregate view for multi-workspace orgs. This lets an agent separate it from get_citation_sources without opening either schema.

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

Usage Guidelines5/5

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

Gives concrete user phrasings that select this tool ('across all workspaces', 'org-wide sources', 'top domains overall') and names the alternative plus the condition that selects it: 'For one workspace, use get_citation_sources.' Both when-to-use and when-not-to-use are present.

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