Skip to main content
Glama
Sign In

Rempa

by ai.rempa
OverviewDiscussionsAdmin

Get a project

get_project
Read-only

Get a project's setup: the brand (name, other names, website, market, profile), the competitors tracked, the AI models asked (their ids are the values for the model filter of the other tools) and the topics of the latest update (values for the topic filter). Use it to know what a project tracks; for results, 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_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesThe project: its id or its address (for example "acme-france"), as returned by list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. First observed

TDQS

A4.2/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 trailing 'Read-only.' merely restates them. The description does add real workflow context — that model ids and topics feed the filters of other tools — but says nothing about behavior when a project id is unknown or about response shape beyond the field list.

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?

One front-loaded sentence plus a short routing clause; nothing is wasted. The parenthetical field lists are dense, but each maps to actual returned data rather than filler.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the four content groups. Combined with the routing note and the single documented parameter, an agent has everything needed to call it 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 the single `project` parameter already documents id-or-address with an example. The description adds no further syntax or resolution rules, so the 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?

Specific verb + resource ('Get a project's setup') followed by an enumeration of exactly what is returned: brand fields, competitors, AI models, topics. It is clearly distinguished from get_overview, which covers results rather than configuration.

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?

Explicitly states when to use it ('to know what a project tracks') and names the alternative with its condition ('for results, use get_overview'). It also tells the agent why it would call this first: the returned model ids and topics are the filter values for the other tools.

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