Skip to main content
Glama

InProcess Cockpit

Les offres

offres
Read-only

Les offres d'InProcess avec leurs prix, crédits et cockpits en ligne, pour conseiller la personne.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already declares this a safe read, so the description's added value lies in disclosing the returned content — prices, credits, cockpits. That is genuinely useful given there is no output schema, but it stops short of describing data volume, ordering, or format.

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?

A single front-loaded sentence enumerating the payload followed by a short purpose clause; nothing is redundant. It is efficient, though arguably too terse for a tool with no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless read-only tool with no output schema, the description must carry the return-value burden, and it only sketches the returned fields without structure or granularity. It is adequate to get an agent to call it, but not to predict the response shape.

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 an empty object, so there is no parameter meaning to add. The baseline for a parameterless tool applies.

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

Purpose3/5

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

The description names the resource (InProcess offers) and enumerates its content — prices, credits, online cockpits — which tells an agent what the tool surfaces. However, no verb is given ('list', 'fetch'), so the operation itself is only implied, and the plural 'offres' is not distinguished from the sibling 'mon_offre'.

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

Usage Guidelines3/5

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

'pour conseiller la personne' gives an implied usage context: retrieve offers when advising someone. There is no explicit when-not-to-use statement and no named alternative such as 'mon_offre', so the guidance remains inferential.

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