Skip to main content
Glama

Outil.io

Get signature status

get_signature_status
Read-only

Statut de signature (draft, sent, viewed, signed, declined, expired), preuves (nom, e-mail, IP, horodatage, empreinte) et pdfUrl : après signature, PDF signé + certificat de preuve.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description goes beyond them by disclosing what is returned — proof evidence fields (name, email, IP, timestamp, fingerprint) and pdfUrl — and the important behavioral fact that signed PDF and proof certificate only exist after signing, which is genuinely useful for interpreting empty results.

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?

It is a single compact, front-loaded statement with the status enumeration first and the post-signature artifacts last. Dense formatting (a colon followed by parenthetical field lists) is slightly telegraphic but nothing is wasted.

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 one-parameter read-only getter the description covers return content well, which matters since there is no output schema. The decisive gap is that it never says what the required 'id' identifies, leaving an agent unable to be sure it is passing the right value.

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% for the single required parameter 'id', and the description never explains what that identifier refers to (signature request id, document id, or something else). With low coverage the description is expected to compensate, and it does not.

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 resource precisely (signature status) and enumerates the possible states (draft, sent, viewed, signed, declined, expired), which is far more specific than the bare title. It doesn't name a sibling, but its read-only status-retrieval role is clearly separable from write siblings like request_signature.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is mentioned. The only implicit cue is 'après signature', which hints the PDF/certificate portion is only populated post-signing, but an agent gets no routing help from the text itself.

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.