Skip to main content
Glama

pulsenetwork

by com.theaslangroupllc.pulse
OverviewDiscussionsAdmin

legalpulse

LegalPulse: The clearance layer before you sign, brand, send, or sue — 12 endpoints for legal agents and the people they work for. Pre-signature contract clearance with verbatim red-flag quotes ($0.50), trademark knock-out checks verified live against USPTO TSDR ($0.50), ready-to-send demand letters with statute citations ($2), tenant/employment/consumer rights, small claims, business formation, estate, IP. Jurisdiction-aware.

Coverage: Global

Endpoints: • letter ($2.00): Advocacy letter writer • contract ($0.10): Contract clause review • tenant ($0.10): Tenant rights by state • employment ($0.10): Employment law rights • business ($0.10): Business formation comparison • estate ($0.10): Estate planning checklist • consumer ($0.10): Consumer rights — FDCPA, FCRA, FTC • small-claims ($0.08): Small claims court guide • ip ($0.10): Intellectual property guide • rights ($0.08): Know your rights • sign-check ($0.50): Pre-signature contract clearance • trademark-check ($0.50): Trademark knock-out check w/ live USPTO verification • letter-triage ($0.25): Letter-engine triage (agent-tier preview) • trademark-precheck ($0.25): Trademark precheck (agent-tier preview)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoResponse language code (en | es | fr | de | zh | hi | ar | pt | ja | ko | etc.)
markNothe brand/product name to check
roleNowhich party you are — freelancer | tenant | employee | customer | vendor | ...
textNothe contract text, URL-encoded (or send as POST JSON body {"text":"..."}); min 200 chars, max 30000
typeNotype
goodsNowhat it will be sold as — sharpens class analysis
issueNoissue
stateNostate
actionYesWhich endpoint to call. Options: letter | contract | tenant | employment | business | estate | consumer | small-claims | ip | rights | sign-check | trademark-check | letter-triage | trademark-precheck
amountNoamount
clauseNoclause
serialNooptional CSV of known USPTO serial/registration numbers to verify directly
outcomeNooutcome
concernsNooptional — anything specific to check
recipientNorecipient
situationNosituation
entity_typeNoentity_type
jurisdictionNooptional — auto-detected from the document if omitted
contract_typeNocontract_type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Which endpoint to call. Options: letter | contract | tenant | employment | business | estate | consumer | small-claims | ip | rights | sign-check | trademark-check"New value: +"Which endpoint to call. Options: letter | contract | tenant | employment | business | estate | consumer | small-claims | ip | rights | sign-check | trademark-check | letter-triage | trademark-precheck"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "letter",
-  "contract",
-  "tenant",
-  "employment",
-  "business",
-  "estate",
-  "consumer",
-  "small-claims",
-  "ip",
-  "rights",
-  "sign-check",
-  "trademark-check"
-]New value: +[
+  "letter",
+  "contract",
+  "tenant",
+  "employment",
+  "business",
+  "estate",
+  "consumer",
+  "small-claims",
+  "ip",
+  "rights",
+  "sign-check",
+  "trademark-check",
+  "letter-triage",
+  "trademark-precheck"
+]
  2. Changed5 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Which endpoint to call. Options: letter | contract | tenant | employment | business | estate | consumer | small-claims | ip | rights | sign-check"New value: +"Which endpoint to call. Options: letter | contract | tenant | employment | business | estate | consumer | small-claims | ip | rights | sign-check | trademark-check"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "letter",
-  "contract",
-  "tenant",
-  "employment",
-  "business",
-  "estate",
-  "consumer",
-  "small-claims",
-  "ip",
-  "rights",
-  "sign-check"
-]New value: +[
+  "letter",
+  "contract",
+  "tenant",
+  "employment",
+  "business",
+  "estate",
+  "consumer",
+  "small-claims",
+  "ip",
+  "rights",
+  "sign-check",
+  "trademark-check"
+]
    • addedInput schema / properties / goods
      Added value: +{
+  "description": "what it will be sold as — sharpens class analysis",
+  "type": "string"
+}
    • addedInput schema / properties / mark
      Added value: +{
+  "description": "the brand/product name to check",
+  "type": "string"
+}
    • addedInput schema / properties / serial
      Added value: +{
+  "description": "optional CSV of known USPTO serial/registration numbers to verify directly",
+  "type": "string"
+}
  3. Changed6 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Which endpoint to call. Options: letter | contract | tenant | employment | business | estate | consumer | small-claims | ip | rights"New value: +"Which endpoint to call. Options: letter | contract | tenant | employment | business | estate | consumer | small-claims | ip | rights | sign-check"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "letter",
-  "contract",
-  "tenant",
-  "employment",
-  "business",
-  "estate",
-  "consumer",
-  "small-claims",
-  "ip",
-  "rights"
-]New value: +[
+  "letter",
+  "contract",
+  "tenant",
+  "employment",
+  "business",
+  "estate",
+  "consumer",
+  "small-claims",
+  "ip",
+  "rights",
+  "sign-check"
+]
    • addedInput schema / properties / concerns
      Added value: +{
+  "description": "optional — anything specific to check",
+  "type": "string"
+}
    • addedInput schema / properties / jurisdiction
      Added value: +{
+  "description": "optional — auto-detected from the document if omitted",
+  "type": "string"
+}
    • addedInput schema / properties / role
      Added value: +{
+  "description": "which party you are — freelancer | tenant | employee | customer | vendor | ...",
+  "type": "string"
+}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "the contract text, URL-encoded (or send as POST JSON body {\"text\":\"...\"}); min 200 chars, max 30000",
+  "type": "string"
+}
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does well: it discloses pricing per endpoint, live USPTO verification, verbatim red-flag quotes, statute citations, jurisdiction awareness, and global coverage. This gives the agent a rich understanding of the tool's behavior and potential side effects (costs, external verification).

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?

The description is fairly long but well-structured with a clear intro and a bulleted list of endpoints with prices and brief explanations. The marketing-style opening sentence ('clearance layer') is somewhat unnecessary, but the overall structure makes it easy to scan and extract the key information.

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?

Given 19 parameters and no output schema, the tool is complex. The description gives a good high-level overview and endpoint breakdown, but it lacks explicit guidance on which parameters to provide for each action, and the schema's placeholder descriptions for many parameters leave gaps. Some endpoints like 'letter-triage' are vaguely described as 'agent-tier preview', which is not fully explained.

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?

Although schema coverage is 100%, many parameter descriptions are tautological (e.g., 'type', 'issue', 'outcome', 'recipient', 'situation') and add no real semantic value. The tool description lists endpoints but does not map which parameters are relevant to which action, so it does not compensate for the weak schema descriptions.

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 description clearly states LegalPulse as a legal clearance layer for signing, branding, sending, or suing, with a specific set of endpoints (contract review, trademark knock-out, demand letters, etc.). This distinguishes it from sibling 'pulse' tools and makes the domain and primary use case explicit.

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 description provides clear context for when to use the tool (pre-signature clearance, trademark checks, demand letters) and even lists each endpoint with a brief explanation of its purpose. However, it does not explicitly mention when not to use it or compare against alternative sibling tools, so it misses some exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All pulsenetwork toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources