Skip to main content
Glama

WritersLogic verifiable AI agents

patent-design-around

Patent Design-Around & Freedom-to-Operate Architect — Paste patent claims or give a patent number. Splits the independent claims into lettered limitations in code, charts your product against each one (literal and doctrine of equivalents), scores claims under the all-elements rule, and proposes 3 engineering design-arounds that each remove a limitation of every independent claim, checked in code. Leads with a decision and optional dollar exposure. A

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": {
      "proposedProductDescription": "<proposedProductDescription>"
    },
    "name": "patent-design-around"
  }
}

Input Schema

NameRequiredDescriptionDefault
jurisdictionNoDefaults to US.
patentNumberNoPublication number such as US7629993B2. Used to read the claims from Google Patents when patentClaimsText is omitted.
annualRevenueUsdNoAnnual revenue that depends on the product; sizes the dollar exposure in the headline.
patentClaimsTextNoNumbered claims (at least the independent claims). Optional when patentNumber is given: the claims are then read from Google Patents.
assumedRoyaltyPctNoAssumed running royalty as a percent of revenue, for the exposure illustration.
proposedProductDescriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the analysis pipeline (lettered limitation split, literal plus doctrine-of-equivalents charting, all-elements rule scoring, three code-checked design-arounds) and what the output leads with. It still does not describe the full response shape, any disclaimers, or how ambiguity in claim text is handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core is a single dense sentence that is front-loaded with the verb and resource, which is good. However it is a run-on cramming six pipeline steps together, and the description ends with a dangling truncated fragment ('A ') that is clearly a generation artifact.

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 six-parameter analytical tool with no output schema and no annotations, the description covers inputs and process but leaves the return structure largely implicit beyond 'leads with a decision and optional dollar exposure'. It does not address reliability caveats, jurisdiction breadth, or what happens when claim parsing fails, all of which matter for a legal-analysis tool.

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 coverage is 83%, so the schema already documents all six parameters well, and the description only echoes the claims-vs-patent-number choice and the dollar exposure sizing. It adds little interpretation beyond what the schema descriptions state, which is the expected baseline here.

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?

Description names a specific compound capability (design-around plus freedom-to-operate) and enumerates its constituent steps, so the resource and verb are unambiguous. It does not explicitly contrast itself with sibling tools such as prior-art-invalidator or patent-strategy, which keeps it short of a 5.

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?

The opening line gives the two acceptable input modes ('Paste patent claims or give a patent number'), which is genuinely useful invocation guidance. There is no statement of when this tool is the wrong choice versus patent-strategy or prior-art-invalidator, and no prerequisites or scope exclusions.

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