Skip to main content
Glama

Outil.io

List contract templates

list_contract_templates
Read-only

Modèles de contrat intégrés (prestation-services…) et personnalisés, avec leurs variables. Un modèle personnalisé se crée par create_record type contract_templates {name, html avec {{variables}}, variables:[{key,label,required}]}.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that both built-in and custom templates are returned together with their variables, which is useful output context, but says nothing about ordering, volume or whether anything is filtered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is tight and front-loads the substance. The second sentence documents another tool's payload (create_record with name/html/variables), which is tangential here and dilutes the focus, even if it may be useful routing context.

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 zero-parameter read tool with full annotation coverage the description is close to adequate, and it does say what comes back (templates plus variables). It is not complete on grouping of built-in vs custom results, ordering, or how this list relates to the other template-list siblings.

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?

This tool takes zero parameters, so the baseline is 4 and there is nothing for the description to compensate for. The schema details quoted in the second sentence belong to create_record, not to this tool's inputs.

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 names the specific resource (built-in and custom contract templates) and says it includes their variables, which is more than the title alone. It does not distinguish this from sibling list tools such as list_managed_templates, list_site_templates or list_website_templates, so an agent cannot route between them from this text.

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

Usage Guidelines2/5

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

There is no statement of when to choose this tool over the several sibling template-listing tools. The only guidance is about creating a custom template via create_record, which describes a different operation rather than when to call this one.

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.