Skip to main content
Glama

Create an md2sign account

create_account

Create an md2sign account for your human and get an API key. They are emailed a confirmation link and subscription options. Once they confirm their email they pick a plan at checkout; if account.trial.available is true it starts with a 7-day free trial (card taken, not charged until it ends; 3 envelopes, up to 5 signers each), otherwise it is charged at checkout. Plans: Solo Lite $45/year for 60 envelopes a year, Solo $7.50/mo for 30 a month, Team $19/mo for 100 with team features, Business+ $39/mo for 500; one envelope is one document sent, however many sign. You can validate, draft, preview and test-send right away. Returns api_key, checkout_urls (monthly) and annual_checkout_urls (yearly; Solo Lite is only here) to hand to the human.

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": {
      "name": "<name>",
      "email": "<email>"
    },
    "name": "create_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe full name of your human, as they want recipients to see it. Ask them; don't guess it from the email address.
emailYesEmail address of your human. Document emails show it as the sender.
company_nameNoBusiness name shown to recipients, e.g. "Acme Pty Ltd". Ask whether they have one; leave it out to use their own name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / company_name / description
      Previous value: -"Company name shown to recipients, e.g. \"Acme Pty Ltd\"."New value: +"Business name shown to recipients, e.g. \"Acme Pty Ltd\". Ask whether they have one; leave it out to use their own name."
    • changedInput schema / properties / name / description
      Previous value: -"The full name of your human."New value: +"The full name of your human, as they want recipients to see it. Ask them; don't guess it from the email address."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare the mutation profile (readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive), while the description supplies the real behavioral context: the human receives a confirmation email, the account is not usable until confirmation, and billing depends on account.trial.available (card taken but not charged during a 7-day trial with 3 envelopes / 5 signers, otherwise charged at checkout). That is substantial disclosure well beyond the annotations.

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?

Purpose and return values are front-loaded, and the pricing detail is dense but purposeful since the agent must relay plan options to the human. The plan enumeration (Solo Lite through Business+) is the one passage that could be condensed, though it carries decision-relevant information.

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 correctly explains the return payload (api_key, checkout_urls, annual_checkout_urls) and notes Solo Lite is annual-only, which prevents a routing mistake. It leaves minor ambiguity about whether the api_key is returned before or after email confirmation and says nothing about failure cases such as an email already being registered.

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?

Schema description coverage is 100% and the field descriptions are already strong, including the instruction to ask the human for their name rather than guessing from the email. The description adds no parameter-level detail of its own, so the baseline of 3 applies.

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?

The opening sentence names a specific verb and resource ("Create an md2sign account") and states the outcome ("get an API key"), which cleanly separates it from sibling tools like create_draft or create_document_from_template. An agent can tell this is a one-time account bootstrap, not a document operation.

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?

Usage is implied rather than stated: "for your human" plus the API-key payoff signals this is the setup step before validate/draft/preview/test-send. There is no explicit when-not guidance, such as what to do if the human already has an account (e.g. use get_account or update_account instead), so the agent must infer the prerequisite logic.

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.