Rempa

Get the cited websites

get_sources

Read-only

List the websites the AI answers of one update cite, most cited first: per website, the number and share of answers citing it, its citation count and whether it is the brand's own site. Use it to find the review sites, directories and media to be listed on; to see which answers cite one website, use list_answers with its website filter. Read-only.

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": {
      "project": "<project>"
    },
    "name": "get_sources"
  }
}

Input Schema

Name	Required	Description
`limit`	No	At most this many websites, from 1 to 500. Default 50.
`model`	No	An AI model id from get_project (ai_models[].id, for example "chatgpt" or "gemini"), to keep only that model's answers. Default: all models.
`topic`	No	A topic name or id from get_project (topics), to keep only that topic's prompts. Default: all topics.
`update`	No	An update (run) id from list_updates, to read an earlier update. Default: the latest update.
`project`	Yes	The project: its id or its address (for example "acme-france"), as returned by list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 21, 2026

changedInput schema / properties / limit / description

Previous value: -"At most this many websites. Default 50."New value: +"At most this many websites, from 1 to 500. Default 50."

changedInput schema / properties / model / description

Previous value: -"An AI model id (for example \"chatgpt\", \"gemini\") to keep only its answers. See get_project."New value: +"An AI model id from get_project (ai_models[].id, for example \"chatgpt\" or \"gemini\"), to keep only that model's answers. Default: all models."

changedInput schema / properties / project / description

Previous value: -"The project: its id, or its address (for example \"acme-france\"). See list_projects."New value: +"The project: its id or its address (for example \"acme-france\"), as returned by list_projects."

changedInput schema / properties / topic / description

Previous value: -"A topic name or id to keep only its prompts. See get_project."New value: +"A topic name or id from get_project (topics), to keep only that topic's prompts. Default: all topics."

changedInput schema / properties / update / description

Previous value: -"An update (run) id from list_updates. Default: the latest update."New value: +"An update (run) id from list_updates, to read an earlier update. Default: the latest update."

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description's 'Read-only' merely restates that. It does add value by enumerating the returned fields (count, share of answers, citation count, brand-own flag) and the sort order, but says nothing about pagination, rate limits, or behavior when an update has no citations.

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

Conciseness5/5

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

One front-loaded sentence gives scope, ordering and return fields; a second routes to the alternative; a two-word tag closes it. No wasted clauses.

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?

No output schema exists, but the description compensates by listing the per-website metrics returned, and the schema covers all five parameters with defaults. An agent has enough to call it and interpret results correctly.

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 coverage is 100% and every parameter already carries a description, so the schema does the heavy lifting. The description only implies the update scoping ('answers of one update') without adding syntax or format detail beyond the schema. Baseline 3 applies.

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 the verb (list), the exact resource (websites cited by the AI answers of one update), the ordering (most cited first) and the per-row fields. This distinguishes it clearly from sibling list tools like list_answers, which the description explicitly contrasts.

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 a concrete use case (finding review sites, directories and media to be listed on) and names the alternative plus the condition that selects it: to see which answers cite one website, use list_answers with its website filter. No inference required.

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

All Rempa tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?