Skip to main content
Glama
Sign In

Rempa

by ai.rempa
OverviewDiscussionsAdmin

Get the history

get_history
Read-only

Get the trend over time: per update date, the visibility, average position, sentiment (0 to 100, 50 neutral) and share of voice of the brand and of up to 6 main competitors. Use it for "are we progressing?" or to see whether a change paid off; for one update in detail, use get_overview. 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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
projectYesThe project: its id or its address (for example "acme-france"), as returned by list_projects.
updatesNoHow many of the latest updates to include, from 1 to 365. Default 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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 / updates / description
      Previous value: -"How many of the latest updates. Default 30."New value: +"How many of the latest updates to include, from 1 to 365. Default 30."
  2. 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 readOnlyHint=true, so the trailing 'Read-only.' is confirming rather than adding. The valuable addition is disclosure of the output content and the sentiment scale (0-100, 50 neutral), which the agent cannot get from any structured field since there is no output schema. It stops short of describing aggregation or missing-data behavior.

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?

Two information-dense sentences with the scope and the metric list front-loaded, followed by usage and the alternative. The closing 'Read-only.' is near-redundant given the readOnlyHint annotation but costs only a few words.

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 read-only analytics tool with four fully documented parameters and no output schema, the description covers what the agent needs: what data comes back, the sentiment scale, and competitor coverage. It could say more about how updates are ordered or what happens with sparse data, but nothing required for correct invocation is missing.

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%, so every parameter (model, topic, project, updates) is already documented with defaults and provenance in the schema. The description only alludes to the updates dimension via 'per update date' and adds no format or constraint detail beyond it, so 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 a specific verb and resource ('get the trend over time') and enumerates exactly what is returned per update date: visibility, average position, sentiment, and share of voice for the brand and up to 6 competitors. The scope (per update date, brand vs. competitors) makes it clearly distinct from siblings like get_overview and get_perception.

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 use scenarios ('are we progressing?', 'whether a change paid off') and names the alternative for a different need: 'for one update in detail, use get_overview.' The routing decision is fully determined without opening either schema.

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