Skip to main content
Glama

TenderWatch, marchés publics

Définition d'un terme des marchés publics

definition_marches_publics
Read-only

Donne la définition sourcée (code de la commande publique) d'un terme des marchés publics : DCE, CCAG, standstill, retenue de garantie, avance, offre anormalement basse, etc.

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": {
      "terme": "<terme>"
    },
    "name": "definition_marches_publics"
  }
}

Input Schema

NameRequiredDescriptionDefault
termeYesLe terme, ex. « DCE » ou « retenue de garantie ».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety and closed-corpus behavior are covered. The description adds genuine context beyond that: answers are sourced from the code de la commande publique, so the agent knows the grounding and the legal scope of the knowledge base.

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?

A single sentence with the function stated first and the term examples appended as scoping detail. Nothing is redundant or padded.

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 one-parameter, read-only lookup with no output schema, the description gives enough to call it correctly and knows the answer is source-grounded. It leaves unaddressed what happens for an unknown or out-of-scope term, which is a minor gap for a tool whose return value needs no explanation.

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?

Only one parameter, and the schema documents it fully (100% coverage) with its own examples. The description's term examples reinforce but do not extend that; no guidance on how to phrase partial or ambiguous terms, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Donne la définition sourcée ... d'un terme des marchés publics', plus a concrete list of covered terms (DCE, CCAG, standstill, retenue de garantie...). This makes the tool unmistakable versus the sibling tools, which compute, look up procedures, or search tenders, though no sibling is named explicitly.

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?

There is no explicit 'use this when...' or 'do not use for...' statement, and no alternative is named. Usage is only implied by the sample term list, which tells the agent what kind of vocabulary it can ask about.

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