Free, no-signup e-signatures. check_status free for anyone; find_documents needs paid key.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clear and unique.
The tool name 'check_status' follows a clear verb_noun pattern and is internally consistent, even though it's the only tool.
The server exposes only one tool, which is too few for a service named 'docracy' that implies handling Docracy signing chains. A broader set of operations (e.g., create, list, cancel) would be expected, so the count feels insufficient.
The tool only checks status from an existing link, but lacks any way to create or manage signing chains. Agents cannot initiate workflows or access other essential data, leaving significant gaps in the tool surface.
check_statusCheck signing statusAInspectLook up the status of a Docracy signing chain from a sign or status link — who's signed, who's still pending.
| Name | Required | Description | Default |
|---|---|---|---|
| link | Yes | The docracy.io sign or status link (or just the token) you were emailed. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The phrase 'Look up' implies a read-only operation, but the description does not explicitly state that it has no side effects, nor does it mention authentication requirements, error behavior, or what happens with invalid links. Since annotations are absent, the description carries the burden and covers the basic read-only nature but lacks deeper behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that directly states the action and the information returned. It contains no fluff or redundant wording, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple status-lookup tool with one parameter and no output schema, the description sufficiently explains the outcome ('who's signed, who's still pending'). It lacks details on exact response formatting or edge cases, but given the simplicity, it covers the essential context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides 100% coverage for the 'link' parameter, describing it as a docracy.io sign/status link or token. The description's mention of 'from a sign or status link' aligns with the schema but does not add additional semantic meaning beyond what the schema already states, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Look up' and identifies the resource as 'status of a Docracy signing chain,' making the tool's purpose unmistakable. It also adds context that it works from a sign or status link, which further clarifies its scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly implies when to use the tool: when you have a sign or status link and need to know who has signed and who is pending. There are no explicit exclusions or alternatives, but the context is clear and self-contained.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
