Skip to main content
Glama

Rouage

Services de Rouage

services
Read-only

À utiliser quand l'utilisateur demande ce que fait Rouage ou cherche une formalité de société en France. Liste les formalités juridiques que Rouage réalise en ligne pour les dirigeants en France (fermer une micro-entreprise ou une société, créer une société, approuver les comptes, transférer un siège, augmenter le capital, transformer une société, business plan) avec le lien de chaque service. Lecture seule : ne transmet aucune donnée et ne crée rien.

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": "services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and the description reinforces this by stating that the tool is read-only, transmits no data, and creates nothing. That adds useful privacy and side-effect context, but it does not describe return structure beyond listing services with links, nor does it discuss pagination, ordering, or rate limits.

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?

The description is front-loaded with the usage condition and then states the service listing and read-only behavior. The parenthetical list of formalities is long but directly clarifies scope, and no sentence appears redundant.

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?

For a zero-parameter read-only listing tool with no output schema, the description explains both when to use it and what it returns: legal formalities with a link for each service. It also covers the safety profile, so an agent has enough context to select and invoke it correctly.

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?

The tool takes zero parameters and the schema is empty, so there are no parameter semantics to clarify. The description appropriately does not invent parameter details, keeping the baseline score of 4 for a parameterless tool.

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

Purpose4/5

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

The description states a specific verb and resource: it lists the legal formalities Rouage performs online for company directors in France, with a link for each service. It also gives concrete examples such as closing a micro-enterprise, creating a company, and approving accounts. However, it does not explicitly distinguish this listing tool from the action-oriented siblings commander_business_plan or commander_radiation_micro.

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

Usage Guidelines4/5

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

The opening sentence clearly states when to use the tool: when the user asks what Rouage does or seeks a company formality in France. It does not explicitly name alternatives or say when not to use it, but the read-only disclaimer implies this is for discovery rather than execution.

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