Skip to main content
Glama

E-signature law for a US state

esign_law_lookup

High-level ESIGN / UETA / ESRA summary for a US state, the document types the federal act excludes, and what Docuflex records. Not legal advice.

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": {
      "state": "<state>"
    },
    "name": "esign_law_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter code or state name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the content scope, exclusion categories, and a legal disclaimer, but it does not describe source authority, currency of the summary, response format, or any access constraints. For a low-risk read-only lookup this is adequate but incomplete.

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?

The description is a single front-loaded sentence that states the summary scope, exclusions, and disclaimer without filler. Every clause contributes useful information and there is no redundant wording.

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?

For a one-parameter informational tool with no output schema and no annotations, the description is mostly complete: it says what topics are covered and includes a clear legal disclaimer. It could be richer about return content or source authority, but the remaining gap is minor given the tool's low complexity.

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%, with the sole 'state' parameter already documented as accepting a two-letter code or state name. The description adds no further parameter semantics beyond what the schema provides, so the baseline score of 3 applies.

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 clearly states the resource and scope: a high-level ESIGN/UETA/ESRA summary for a US state, including excluded document types and what Docuflex records. It lacks an explicit action verb like 'look up' or 'retrieve', but the purpose is still easy to distinguish from transactional siblings such as create_envelope or get_envelope.

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 by the informational framing and the 'Not legal advice' disclaimer, but there is no explicit guidance on when to use this tool versus alternatives or when not to use it. An agent can infer this is for compliance-law reference rather than envelope operations, but the description does not state that directly.

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.

Resources