Skip to main content
Glama

Outil.io

Request signature

request_signature

Figer et numéroter (CTR-AAAA-NNNN) un contrat, calculer son empreinte SHA-256 et renvoyer signUrl (signature en ligne : nom, tracé, consentement, horodatage, IP) et pdfUrl. N’envoie aucun e-mail. Les devis se signent directement depuis leur publicUrl.

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": {
      "id": "<id>"
    },
    "name": "request_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
expiresInDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say this is a non-destructive write with no open-world access; the description adds what actually happens: the contract is frozen and numbered, a SHA-256 hash is computed, both signUrl and pdfUrl are returned, and no e-mail is sent. It even enumerates what the online signature captures (name, drawing, consent, timestamp, IP), which is exactly the kind of behavior an agent cannot infer from annotations.

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?

Three compact sentences, each carrying distinct information: the core action, the returned artifacts, and the exclusions. Nothing is repeated from the title or annotations, and the main action is front-loaded.

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 usefully names the return values (signUrl, pdfUrl) and there are annotations covering the safety profile, so the tool is callable. The remaining gap is the undocumented expiresInDays parameter, which matters for a signing link whose lifetime is bounded.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, yet it never mentions 'id' (which contract) or 'expiresInDays' (the 1-365 signature validity window). The implied contract target and expiry are only loosely guessable from the described behavior, leaving the one optional parameter entirely unexplained.

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?

States specific verbs and outcomes: freeze and number the contract as CTR-AAAA-NNNN, compute a SHA-256 fingerprint, and return signUrl and pdfUrl. It also separates contracts from quotes ('les devis se signent directement depuis leur publicUrl'), so an agent can tell which flow applies without consulting a sibling schema.

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 exclusion 'les devis se signent directement depuis leur publicUrl' tells the agent when NOT to call this tool, and 'N'envoie aucun e-mail' sets expectations about side effects. It stops short of pointing to get_signature_status for follow-up or stating prerequisites such as contract state or permissions.

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.