Skip to main content
Glama
Sign In
Patent PreCheck

Patent PreCheck

Official
by Patent-PreCheck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Patent PreCheck — score patentability

precheck_score

Assess patentability of source code or invention description, generating pillar scores, prior-art count, and rejection patterns.

Instructions

Run a patentability pre-check on source code or an invention description. Returns pillar scores, band, opportunities, prior-art count, rejection patterns, and legal context when available. Provide code or path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "precheck_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoSource code or invention description (>= 10 chars).
pathNoPath to a local file to read and analyze instead of passing `code` inline.
filenameNoOptional filename hint (e.g. main.ts).
tierNoAnalysis tier. Defaults to free.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • changedInput schema / properties / code / description
      Previous value: -"The source code or invention description to analyze (>= 10 chars)."New value: +"Source code or invention description (>= 10 chars)."
    • changedInput schema / properties / filename / description
      Previous value: -"Optional filename hint (e.g. main.ts) used for language/context."New value: +"Optional filename hint (e.g. main.ts)."
    • changedInput schema / properties / tier / description
      Previous value: -"Analysis tier. Defaults to free; paid tiers require server-side entitlement."New value: +"Analysis tier. Defaults to free."
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description should disclose behavioral traits like safety (read-only), authentication needs, or side effects. The description only mentions what it returns, not whether it modifies state or requires permissions. 'Pre-check' implies non-destructive, but it is not explicit.

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 two succinct sentences, front-loaded with the action verb 'Run'. Every sentence adds necessary information without any fluff. Ideal length for clarity.

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?

Given the tool has 4 parameters, no output schema, and no annotations, the description adequately covers purpose and return values. However, it could be more complete by specifying the output format (e.g., JSON structure) or error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by explicitly noting to 'provide code or path', guiding the agent to choose one of those two parameters. This constraint is not present in the schema, so the description improves parameter semantics.

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 tool runs a patentability pre-check on source code or invention description and enumerates the types of results returned. However, it does not differentiate from sibling tools like precheck_pillars or precheck_prior_art, which might be subsets of this compound tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lacks any guidance on when to use this tool versus its siblings. It does not provide context such as prerequisites, when it is appropriate, or when to choose an alternative.

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

Deploy Server

Other Tools