Skip to main content
Glama

TenderWatch, marchés publics

Procédure de passation selon le montant

procedure_selon_montant
Read-only

Indique la procédure et la publicité applicables à un marché public selon son montant HT, sa nature et le type d'acheteur (seuils de dispense, MAPA, procédure formalisée).

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": {
      "montant_ht": "<montant_ht>",
      "nature": "<nature>",
      "acheteur": "<acheteur>"
    },
    "name": "procedure_selon_montant"
  }
}

Input Schema

NameRequiredDescriptionDefault
natureYes
acheteurYes
montant_htYesMontant HT estimé du marché, en euros.

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 this as a read-only, closed-world, non-destructive operation, so the description need not repeat safety details. The description adds that it returns procedure and publicity rules based on thresholds, but it does not disclose the legal basis, jurisdiction, recency of thresholds, or that it is purely advisory.

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 a single, front-loaded sentence that immediately states the action, the decision criteria, and the outcome categories. Every clause earns its place with no redundant framing.

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?

With no output schema, the description carries the burden of explaining what is returned. It adequately states that the tool returns the applicable procedure and publicity rules, and it names the main outcome categories, though it does not describe the return format or legal source.

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 description coverage is only 33%, so the description must compensate for undocumented enum values. It names all three inputs and links them to procurement outcomes, but it does not explain the distinction between 'travaux' and 'fournitures-services' or between 'état', 'collectivite', and 'entite-adjudicatrice' beyond the property names.

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?

The description states a specific decision-support action: it indicates the applicable procurement procedure and publicity rules for a public contract. It names the exact criteria (montant HT, nature, type d'acheteur) and the outcome categories (dispense, MAPA, procédure formalisée), making the tool clearly distinct from siblings such as calculer_interets_moratoires or rechercher_appels_offres.

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?

It clearly implies when to use the tool: when an agent needs to determine the procurement procedure and publicity obligations from contract amount, nature, and buyer type. It does not explicitly state exclusions or name an alternative sibling tool, but the domain and decision context are unambiguous.

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