Skip to main content
Glama
Sign In

Rempa

by ai.rempa
OverviewDiscussionsAdmin

List answers

list_answers
Read-only

List the AI answers of one update, one row per prompt and AI model: the prompt, its topic, the model, whether the brand is named and at which position, whether its website is cited, the brands named and the source URLs. Filter by model, topic, a brand named or a website cited, for example to find the prompts where a competitor is named and the brand is not. Paginated: total and next_offset tell whether more remain. Rows hold no answer text; use get_answer with an answer_id for it. 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": "list_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoOnly the answers naming this brand (the project's or a competitor's name, as in get_overview). Default: all answers.
limitNoAt most this many answers, from 1 to 200. Default 50.
modelNoAn AI model id from get_project (ai_models[].id, for example "chatgpt" or "gemini"), to keep only that model's answers. Default: all models.
topicNoA topic name or id from get_project (topics), to keep only that topic's prompts. Default: all topics.
offsetNoSkip this many answers; pass the previous next_offset for the next page. Default 0.
updateNoAn update (run) id from list_updates, to read an earlier update. Default: the latest update.
projectYesThe project: its id or its address (for example "acme-france"), as returned by list_projects.
websiteNoOnly the answers citing this website, as a domain such as "g2.com" (a URL also works). Default: all answers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / brand / description
      Previous value: -"Only the answers naming this brand (yours or a competitor)."New value: +"Only the answers naming this brand (the project's or a competitor's name, as in get_overview). Default: all answers."
    • changedInput schema / properties / limit / description
      Previous value: -"At most this many answers. Default 50."New value: +"At most this many answers, from 1 to 200. 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 / offset / description
      Previous value: -"Skip this many answers (for the next page)."New value: +"Skip this many answers; pass the previous next_offset for the next page. Default 0."
    • 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."
    • changedInput schema / properties / website / description
      Previous value: -"Only the answers citing this website, for example \"g2.com\"."New value: +"Only the answers citing this website, as a domain such as \"g2.com\" (a URL also works). Default: all answers."
  2. First observed

TDQS

A4.5/5.0
Behavior4/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 reinforces read-only. Adds real behavioral context: pagination semantics (total and next_offset indicate more remain) and the key limitation that rows contain no answer text. Doesn't discuss rate limits or row ordering, so not a 5.

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?

Front-loads purpose, then row contents, then filters with an example, then pagination, then the get_answer redirect. Dense but each sentence earns its place. The final bare 'Read-only.' is slightly redundant with annotations but harmless.

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 an 8-param list tool with no output schema, the description adequately covers row shape, filtering, pagination, and the critical limitation that answer text is absent. Minor gap: no guidance on ordering or how brand position is represented.

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 coverage is 100%, so baseline is 3; the description adds value by enumerating what each row contains (topic, model, brand named and position, website cited, brands named, source URLs) and framing the filters as selecting on those fields. This gives the agent a mental model for combining brand/website/model/topic filters beyond the schema's per-param text.

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 (list) and resource (AI answers of one update) with row-level shape described (one row per prompt and AI model). Clearly distinguishes itself from get_answer by noting rows hold no answer text and pointing to get_answer with an answer_id.

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 explicit routing: use get_answer for answer text. Provides a concrete usage example ('find the prompts where a competitor is named and the brand is not') that maps filtering to a goal. Names the sibling list_updates implicitly via the update parameter source and get_overview for brand names.

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

All Rempa toolsInspect
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